NAME<\/a> ______________________________________________________________________________<\/p>\n bindtags \u2212 Determine which bindings apply to a window, and order of evaluation<\/p>\n bindtags<\/b> window<\/i> ?tagList<\/i>? ______________________________________________________________________________<\/p>\n When a binding is created with the bind<\/b> command, it is associated either with a particular window such as .a.b.c<\/b>, a class name such as Button<\/b>, the keyword all<\/b>, or any other string. All of these forms are called binding tags<\/i>. 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\u2019s tags in order: for each tag, the most specific binding that matches the given tag and event is executed. See the bind<\/b> command for more information on the matching process.<\/p>\n By default, each window has four binding tags consisting of the name of the window, the window\u2019s class name, the name of the window\u2019s nearest toplevel ancestor, and all<\/b>, in that order. Toplevel windows have only three tags by default, since the toplevel name is the same as that of the window. The bindtags<\/b> command allows the binding tags for a window to be read and modified.<\/p>\n If bindtags<\/b> is invoked with only one argument, then the current set of binding tags for window<\/i> is returned as a list. If the tagList<\/i> argument is specified to bindtags<\/b>, then it must be a proper list; the tags for window<\/i> are changed to the elements of the list. The elements of tagList<\/i> 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 tagList<\/i> determines the order in which binding scripts are executed in response to events. For example, the command<\/p>\n bindtags .b {all . Button .b}<\/b><\/p>\n reverses the order in which binding scripts will be evaluated for a button named .b<\/b> so that all<\/b> bindings are invoked first, following by bindings for .b<\/b>\u2019s toplevel (\u201c.\u201d), followed by class bindings, followed by bindings for .b<\/b>. If tagList<\/i> is an empty list then the binding tags for window<\/i> are returned to the default state described above.<\/p>\n The bindtags<\/b> command may be used to introduce arbitrary additional binding tags for a window, or to remove standard tags. For example, the command<\/p>\n bindtags .b {.b TrickyButton . all}<\/b><\/p>\n replaces the Button<\/b> tag for .b<\/b> with TrickyButton<\/b>. This means that the default widget bindings for buttons, which are associated with the Button<\/b> tag, will no longer apply to .b<\/b>, but any bindings associated with TrickyButton<\/b> (perhaps some new button behavior) will apply.<\/p>\n If you have a set of nested frame<\/b> widgets and you want events sent to a button<\/b> widget to also be delivered to all the widgets up to the current toplevel<\/b> (in contrast to Tk\u2019s default behavior, where events are not delivered to those intermediate windows) to make it easier to have accelerators that are only active for part of a window, you could use a helper procedure like this to help set things up:<\/p>\n proc setupBindtagsForTreeDelivery {widget} { bind(n)<\/p>\n binding, event, tag<\/p>\n bindtags \u2212 Determine which bindings apply to a window, and order of evaluation <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3783,1],"tags":[2845,2635],"class_list":["post-6220","post","type-post","status-publish","format-standard","hentry","category-n-comandos-tcl-tk","category-sin-categoria","tag-bindtags","tag-mann"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6220","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=6220"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6220\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=6220"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=6220"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=6220"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
SYNOPSIS<\/a>
DESCRIPTION<\/a>
EXAMPLE<\/a>
SEE ALSO<\/a>
KEYWORDS<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
EXAMPLE <\/a> <\/h2>\n
set tags [list $widget [winfo class $widget]]
set w $widget
set t [winfo toplevel $w]
while {$w ne $t} {
set w [winfo parent $w]
lappend tags $w
}
lappend tags all
bindtags<\/b> $widget $tags
}<\/p>\nSEE ALSO <\/a> <\/h2>\n
KEYWORDS <\/a> <\/h2>\n
\n","protected":false},"excerpt":{"rendered":"