[RS] writes on comp.lang.tcl: The bind syntax is actually very easy. With x set to a widget (e.g.
.mytext) or a class (e.g. Text), call

bind $x

bind $x <Key-Prior>

bind $x <Control-r> [bind $x <Key-Prior>]

console show

bind .textwidget <KeyPress> { %W insert end "%K\n" }
focus .textwidget

   <Key-keysym>
   <KeyPress-keysym>
   <KeyRelease-keysym> (subtle differences here!)
   <keysym>
   <A>                (if the character is plain ASCII)
For a space, you will need to use:

*** Idea: <Invoke> event ***
** Idea: <Invoke> event **
[Martin Lemburg] July 2nd, 2002:
[Martin Lemburg] 2002-07-02: Why isn't there an event ''Invoke'' for invokeable
I have a question:
Than ...
Why isn't there an event ''Invoke'' for invokeable widgets, like buttons? Wouldn't make it sense to have such an event? To bind widgets using the ''Invoke'' event, like to connect a widget with the ''-command'' option to an event handler?

... would be equal to ...

It shouldn't be a problem to use the substitution capabilities during the usage of a binding, like:

Wouldn't that be nice and consequent?

Wouldn't it be consequent (for example) to use bindings to scrollbars or
Wouldn't it be consequent (for example) to use bindings to scrollbars or entries too? ...

There would be the chance to elimate all (event)handlers from that code, that
There would be the chance to elimate all (event)handlers from that code, that only builds up the GUI. The code to handle events could use now use bindings.

*** caution when using abbreviated binding descriptions ***

[Ken Jones] writes on comp.lang.tcl, in response to a developer trying to bind actions on numeric keys using 
** Caution: Abbreviated `bind` Descriptions **
bind .bu1 <Alt-2> {focus .bu2}
bind .bu1 <Alt-2> "focus .bu2"

What you're experiencing is one of those traps that people encounter when they
the following response:
On the other hand, Tcl also allows you to abbreviate ButtonPress events, so <1>
What you're experiencing is one of those traps that people encounter when they use abbreviated binding descriptions. For many KeyPress events, you can get by with providing only the keysym. So, <a> is equivalent to <KeyPress-a>, and <Control-a> is equivalent to <Control-KeyPress-a>.
Solution? `bind` to `<Alt-KeyPress-1>` and `<Alt-KeyPress-2>`. And be very careful
On the other hand, Tcl also allows you to abbreviate ButtonPress events, so <1> is equivalent to <ButtonPress-1>. And <Alt-1> through <Alt-5> is equivalent to <Alt-ButtonPress-1> through <Alt-ButtonPress-5>.

Solution? Bind to <Alt-KeyPress-1> and <Alt-KeyPress-2>. And be very careful relying on abbreviated event descriptions in bindings.

*** binding so that keypad keys respond ***
** Keypad Keys **
[LV] I am trying to get the following sample program to display the numbers

The expectation was that I would get an entry widget into which I could press
The expectation was that I would get an entry widget into which I could
press the keys on the keypad and get, in this case, the number 1 into
the entry widget.  What I experience is that after I mouse into the
widget and click, I can type alphas and the numbers on top row of the
main keyboard, but the keypad keys are generating nothing...
Peter Newman 2004-04-30: ''NumLock'' switches the keypad between numbers and
Peter Newman 30 April 2004: ''NumLock'' switches the keypad between numbers and cursor keys. I presume you tried both settings - and still no joy. If so, then it would appear that Tk doesn't support the keyboard properly.

Pierre Coueffin 2004-04-12: Try `<KeyPress-KP_1>`
Pierre Coueffin 12 April 2005: Try <KeyPress-KP_1>
Thomas Guettler 26 April 2006: Or Try `<KP_End>`
Thomas Guettler 26 April 2006: Or Try <KP_End>

 % bind Nothing <Button1-ButtonPress-2> {;}
 % bind Nothing
 <B1-Button-2>

***bindings for control sequences***
** Control Sequences **
[Dossy] 29mar2005: I just spent a good hour only trying to understand [[bind]] only to discover that [[bind . <Control-a> {script}]] is NOT the same as [[bind . <Control-A> {script}]] -- the former works, the latter doesn't.
[RS] would expect that <Control-A> is equivalent to <Control-Shift-a> ... case matters, doesn't it?
[Dossy] 2005-03-29: I just spent a good hour only trying to understand `bind`
[MG] The bindings for this, after a little playing, seem slightly strange. Without Caps Lock on, Shift and the 'a' key (to get an upper-case A) fires the binding for Shift and (uppercase) A. The only way to fire a binding for Shift and (lowercase) a that I can find is to turn Caps Lock on, and -then- press the 'a' key with Shift held down.
[RS]: would expect that `<Control-A>` is equivalent to `<Control-Shift-a>` ... case
CJL The minimal example of this mildly unexpected behaviour is to switch Caps Lock on, then in a Wish console (I'm talking Windoze here) type something, highlight it and press Ctrl-C. Now try to paste your text somewhere else (e.g. Notepad) using Ctrl-V - you'll discover that the copy didn't happen, but even though Caps Lock is still on, Notepad will quite happily obey the paste request (by pasting whatever was already in the clipboard). To me 'Ctrl-C' means "the physical key labelled with a 'C' was pressed while ctrl was down", and should have nothing to do with the state of Caps Lock, only the combination of keys pressed.
[MG]: The bindings for this, after a little playing, seem slightly strange.
[WHD]: On both Windows and Mac OS X, normal apps accept both Control-v and Control-V (Command-v and Command-V) as the Paste key.  For Tk, it appears that you need to bind both.  On the other hand, if you bind both you'll find that all of the following combinations will paste:
CJL The minimal example of this mildly unexpected behaviour is to switch Caps
   * Control-v
   * Control-V
   * Shift-Control-v
   * Shift-Control-V
If you want to support Shift-Control sequences in your keyset, you need to bind
If you want to support Shift-Control sequences in your keyset, you need to bind both Shift-Control-v and Shift-Control-V.  Here's a simple solution that results in CapsLock-independent letter key bindings:
i
proc bindletterkey {tag modifier letter binding} {
    set upper [string toupper $letter]
    set lower [string tolower $letter]

    bind $tag <$modifier-$upper> $binding
    bind $tag <$modifier-$lower> $binding
} 

bindletterkey .text Control F       {puts Control-F}
bindletterkey .text Control F       {puts "Control-F"}
bindletterkey .text Shift-Control F {puts "Shift-Control-F"}


** Case Insensitive Binding **
*** Case Insensitive Binding ***
[MG] 2005-06-06:  And, where the bindings already exist (ie, for the Text
[MG] adds, on June 6 2005 - And, where the bindings already exist (ie, for the Text widget) and you want to make them case-insensitive, something like this will help.

Then run, for instance:

It's also careful not to overwrite bindings - if you have an <a> and an <A>
It's also careful not to overwrite bindings - if you have an <a> and an <A> binding for the Text widget, and run ''mirror Text 1'', <A> will be left as it is, rather than being overwritten with <a>'s binding.
This raises one question for me, though - what's better practice? Should you
This raises one question for me, though - what's better practice? Should you bind to
bind Text <A> [bind Text <a>]

bind Text <A> {event generate %W <a>}

trumps

*** Bind to a plain keystroke only (not modified by Ctrl or Alt) ***

proc bind'plainkey {tag key script} { 
    bind $tag <Control-$key> {} 
    bind $tag <Control-$key> { } 
    bind $tag <Alt-$key>     { } 
} 

bind'plainkey all x {puts Hello} 

But it is destroying base if cursor goes near to entry.  Can anybody solve the
But it is destroying base if cursor goes near to entry.
Can anybody solve the problem.

*** how to disable pasting ***
** Disable Pasting **
2008-03-17: How can I disable pasting into a text widget? I tried the following:
2008-03-17: How can I disable pasting into a text widget? I tried the
bind $theText <<Paste>> {tk_messageBox -message {Paste Attempt}}
bind $theText <<Paste>> {tk_messageBox -message "Paste Attempt"}
bind $theText <Control-v> {tk_messageBox -message "Paste Attempt"}
bind $theText <Button-2> {tk_messageBox -message "Paste Attempt"}
bind $theText <Shift-Insert> {tk_messageBox -message "Paste Attempt"}

The message boxes are shown, so the event handling works. But after the message
The message boxes are shown, so the event handling works. But after the message box has been clicked away, the pasting takes place anyway - at least for Shift-Insert.
Answer: You are adding bindings to the widget but aren't addressing the
''You are adding bindings to the widget but aren't addressing the bindings associated with the widget class. Read up on [bindtags]. One solution is to add ";break" to each binding to prevent the class bindings from firing:''

  
Of course, you can also just set the -state option to "disabled".
''Of course, you can also just set the -state option to "disabled".''

----

'''[Janic] - 2009-07-01 09:48:17'''
*** Class binding, do they work? ***


[Janic]: 2009-07-01T09:48:17:
I tried to set a class binding but it never works. For example:
Hi,

bind Checkbutton <ButtonPress> break
bind Checkbutton <ButtonPress> "break"

it doesn't work.  Did I miss something in the class binding behavior?
it doesn't work.
Did I miss something in the class binding behavior?
[MG]: Many different bindings are checked for a widget, based on its
[MG] Many different bindings are checked for a widget, based on its [bindtags].
The default order for a widget is: bindings on the widget itself, bindings on
its class, its toplevel, and then on "all". Also, bindings are checked from
most specific match to least specific (so if you press the 'a' key, it checks
for KeyPress-a before a more generic KeyPress, etc).
That's why you're seeing what you see; first the widget's own bindings are
checked, and the generic `<ButtonPress>` binding matches and is run; `[break]`
checked, and the generic <ButtonPress> binding matches and is run; the [break]

When you `bind` that on the Checkbutton class, though, the default
When you bind that on the Checkbutton class, though, the default
<ButtonPress-1> binding is more specific, and gets used instead of your
<ButtonPress> binding. (You can see all the default bindings with [[bind
Checkbutton]], then see what a specific one does with [[bind Checkbutton
$binding]].) So, to override the default binding, you'd need to either replace
the Button-1 binding, or add something higher up the [bindtags] chain.
[DKF]: You are advised to be ''very'' careful with changing bindings of widget
classes, as that affects ''all'' widgets of that type in the application. (It's
most useful if you're adding more editing keys to the `[text]` [widget], or are
most useful if you're adding more editing keys to the [text] [widget], or are
making your own megawidget class.) It's far better to adjust the [bindtags] for

[wdb]: Here an example: button `.b` has new binding tag,  `Button1` instead of
[wdb] 
Here an example: button .b has new binding tag ''Button1'' instead of
''Button''.  Bindings are copied from ''Button'' to ''Button1'', then binding
of <1> is modified:
===
% package require Tk
8.5.1
% pack [button .b -text Howdy]
% # button appears
% bindtags .b
.b Button . all
% bindtags .b {.b Button1 . all}
% bindtags .b ".b Button1 . all"
  foreach p [bind $old] {
      bind $new $p [bind $old $p]
    }
}} Button Button1
%
% bind Button1 <1> "+puts yep!"
% # now clicking on .b:
% yep!

% 
===

From now on, you can change arbitrary buttons without side-effects to "normal"
From now on, you can change arbitrary buttons without side-effects to "normal" buttons.
----

*** 
'''[telgo] - 2010-07-29 15:22:47'''
[telgo] 2010-07-29 15:22:47:

$Test add command -label Find -accel Command-F -command Find

proc Find {} {
    global body dict t
        global body dict t
        
        set t1 [clock clicks -milliseconds]        
        set f .dictdisplay
        
        #see if we want to restrict display
        set target {}
        if { [$t tag ranges sel] ne "" } {
                set term [$t get sel.first sel.last]
                set target [::soundex::soundex $term]
        } 
        
        if [Dialog_Create $f "Dictionary" -borderwidth 10] {
                set text [Scrolled_Text $f.body -width 20 -font 16]
                set b [frame $f.buttons]
        #--------- convert the array to a list
                #--------- convert the array to a list
                foreach index [array names dict] {
                        lappend sort "$index"
                }
                set sorted [WolofSort $sort]
                foreach item $sorted {
                        if {$target eq {} || $target eq [::soundex::soundex $item] } {
                                  $text insert end "$item : $dict($item)\n"
                        }
                }

                pack $f.body  $f.buttons -side top -fill x
                button $b.ok -text OK -command {set dictdisplay(ok) 1}
                pack $b.ok -side right
        set sorted [WolofSort $sort]
        set t2 [clock clicks -milliseconds]
        puts "[expr ($t2-$t1)/1000.0] seconds"
        
        set dictdisplay(ok) 0
        Dialog_Wait $f dictdisplay(ok) 
        
        set t3 [clock clicks -milliseconds]
        puts "[expr ($t3-$t2)/1000] seconds"
        Dialog_Dismiss $f