1mNAME0m
       bindtags  -  Determine  which  bindings apply to a window, and order of
       evaluation

1mSYNOPSIS0m
       1mbindtags 4m22mwindow24m ?4mtagList24m?


1mDESCRIPTION0m
       When a binding is created with  the  1mbind  22mcommand,  it  is  associated
       either  with  a  particular window such as 1m.a.b.c22m, a class name such as
       1mButton22m, the keyword 1mall22m, or any other string.  All of these  forms  are
       called  4mbinding24m 4mtags24m.  Each window contains 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 window's tags in
       order:  for each tag, the most specific binding that matches the  given
       tag  and  event is executed.  See the 1mbind 22mcommand for more information
       on the matching process.

       By default, each window has four binding tags consisting of the name of
       the  window,  the window's class name, the name of the window's nearest
       toplevel ancestor, and 1mall22m, in that order.  Toplevel windows have  only
       three  tags  by default, since the toplevel name is the same as that of
       the window.  The 1mbindtags 22mcommand allows the binding tags for a  window
       to be read and modified.

       If  1mbindtags 22mis invoked with only one argument, then the current set of
       binding tags for 4mwindow24m is returned as a list.  If the 4mtagList24m argument
       is  specified  to 1mbindtags22m, then it must be a proper list; the tags for
       4mwindow24m are changed to the  elements  of  the  list.   The  elements  of
       4mtagList24m may be arbitrary strings;  however, any tag starting with a dot
       is treated as the name of a window;  if no window by that  name  exists
       at  the  time  an  event is processed, then the tag is ignored for that
       event.  The order of the elements in 4mtagList24m determines  the  order  in
       which binding scripts are executed in response to events.  For example,
       the command
              1mbindtags .b {all . Button .b}0m
       reverses the order in which binding scripts will  be  evaluated  for  a
       button  named  1m.b  22mso that 1mall 22mbindings are invoked first, following by
       bindings for 1m.b22m's toplevel (``.''), followed by  class  bindings,  fol-
       lowed by bindings for 1m.b22m.  If 4mtagList24m is an empty list then the binding
       tags for 4mwindow24m are returned to the default state described above.

       The 1mbindtags 22mcommand may be  used  to  introduce  arbitrary  additional
       binding  tags  for  a window, or to remove standard tags.  For example,
       the command
              1mbindtags .b {.b TrickyButton . all}0m
       replaces the 1mButton 22mtag for 1m.b 22mwith 1mTrickyButton22m.  This means that  the
       default widget bindings for buttons, which are associated with the 1mBut-0m
       1mton 22mtag, will no longer apply to 1m.b22m, but any bindings  associated  with
       1mTrickyButton 22m(perhaps some new button behavior) will apply.


1mSEE ALSO0m
       bind


1mKEYWORDS0m
