When a binding is created with the <B>bindB> command, it is
associated either with a particular window such as $widget,
a class name such as <B>Tk::ButtonB>, the keyword <B>allB>, or any
All of these forms are called binding tags.
Each window has a list of binding tags that determine how
events are processed for the window.
When an event occurs in a window, it is applied to each of the
windows tags in order: for each tag, the most specific binding
that matches the given tag and event is executed.
See the Tk::bind documentation for more information on the matching
By default, each window has four binding tags consisting of the
the windows class name, name of the window, the name of the windows
nearest toplevel ancestor, and <B>allB>, in that order.
Toplevel windows have only three tags by default, since the toplevel
name is the same as that of the window.
Note that this order is different from order used by Tcl/Tk.
Tcl/Tk has the window ahead of the class name in the binding order.
This is because Tcl is procedural rather than object oriented and
the normal way for Tcl/Tk applications to override class bindings
is with an instance binding. However, with perl/Tk the normal way
to override a class binding is to derive a class. The perl/Tk order
causes instance bindings to execute after the class binding, and
so instance bind callbacks can make use of state changes (e.g. changes
to the selection) than the class bindings have made.
The <B>bindtagsB> command allows the binding tags for a window to be
read and modified.
If $widget-><B>bindtagsB> is invoked without an argument, then the
current set of binding tags for $widget is returned as a list.
If the tagList argument is specified to <B>bindtagsB>,
then it must be a reference to and array; the tags for $widget are changed
to the elements of the array. (A reference to an anonymous array can
be created by enclosin the elements in <B>[ ]B>.)
The elements of tagList may be arbitrary strings or widget objects,
if no window exists for an object at the time an event is processed,
then the tag is ignored for that event.
The order of the elements in tagList determines the order in
which binding callbacks are executed in response to events.
For example, the command
applies the Tcl/Tk binding order which binding callbacks will be
evaluated for a button (say) <B>B>$b<B>B> so that <B>B>$b<B>B>s instance bindings
are invoked first, following by bindings for <B>B>$b<B>B>s class, followed by
bindings for <B>B>$b<B>B>s toplevel, followed by <B>allB> bindings.
If tagList is an empty list i.e. <B>B>, then the binding
tags for $widget are returned to the perl/Tk default state described above.
The <B>bindtagsB> command may be used to introduce arbitrary
additional binding tags for a window, or to remove standard tags.
For example, the command
replaces the (say) <B>Tk::ButtonB> tag for <B>B>$b<B>B> with <B>TrickyButtonB>.
This means that the default widget bindings for buttons, which are
associated with the <B>Tk::ButtonB> tag, will no longer apply to <B>B>$b<B>B>,
but any bindings associated with <B>TrickyButtonB> (perhaps some
new button behavior) will apply.