NAME<\/a> ______________________________________________________________________________<\/p>\n busy \u2212 confine pointer events to a window sub-tree<\/p>\n tk busy<\/b> window<\/i> ?options<\/i>?<\/p>\n tk busy hold<\/b> window<\/i> ?options<\/i>?<\/p>\n tk busy configure<\/b> window<\/i> ?option value<\/i>?…<\/p>\n tk busy forget<\/b> window<\/i> ?window<\/i> ?…<\/p>\n tk busy current<\/b> ?pattern<\/i>?<\/p>\n tk busy status<\/b> window<\/i> ______________________________________________________________________________<\/p>\n The tk busy<\/b> command provides a simple means to block pointer events from Tk widgets, while overriding the widget\u2019s cursor with a configurable busy cursor. Note this command does not prevent keyboard events from being sent to the widgets made busy.<\/p>\n There are many times in applications where you want to temporarily restrict what actions the user can take. For example, an application could have a \u201cRun\u201d button that when pressed causes some processing to occur. However, while the application is busy processing, you probably don\u2019t want the user to be able to click the \u201cRun\u201d button again. You may also want restrict the user from other tasks such as clicking a \u201cPrint\u201d button.<\/p>\n The tk busy<\/b> command lets you make Tk widgets busy. This means that user interactions such as button clicks, moving the mouse, typing at the keyboard, etc. are ignored by the widget. You can set a special cursor (like a watch) that overrides the widget\u2019s normal cursor, providing feedback that the application (widget) is temporarily busy.<\/p>\n When a widget is made busy, the widget and all of its descendants will ignore pointer events. It\u2019s easy to make an entire panel of widgets busy. You can simply make the toplevel widget (such as \u201c.\u201d) busy. This is easier and far much more efficient than recursively traversing the widget hierarchy, disabling each widget and re-configuring its cursor.<\/p>\n Often, the tk busy<\/b> command can be used instead of Tk\u2019s grab<\/b> command. Unlike grab<\/b> which restricts all user interactions to one widget, with the tk busy<\/b> command you can have more than one widget active (for example, a \u201cCancel\u201d dialog and a \u201cHelp\u201d button).<\/p>\n EXAMPLE<\/b> frame .top All the widgets within .top<\/b> (including .top<\/b>) are now busy. Using update<\/b> insures that tk busy<\/b> command will take effect before any other user events can occur.<\/p>\n When the application is no longer busy processing, you can allow user interactions again and free any resources it allocated by the forget<\/b> operation.<\/p>\n tk busy<\/b> forget .top<\/p>\n The busy window has a configurable cursor. You can change the busy cursor using the configure<\/b> operation.<\/p>\n tk busy<\/b> configure .top \u2212cursor “watch”<\/p>\n Destroying the widget will also clean up any resources allocated by the tk busy<\/b> command.<\/p>\n The following operations are available for the tk busy<\/b> command: Shortcut for tk busy hold<\/b> command.<\/p>\n tk busy hold<\/b> window<\/i> ?option value<\/i>?…<\/p>\n Makes the specified window<\/i> (and its descendants in the Tk window hierarchy) appear busy. Window<\/i> must be a valid path name of a Tk widget. A transparent window is put in front of the specified window. This transparent window is mapped the next time idle tasks are processed, and the specified window and its descendants will be blocked from user interactions. Normally update<\/b> should be called immediately afterward to insure that the hold operation is in effect before the application starts its processing. The following configuration options are valid: Specifies the cursor to be displayed when the widget is made busy. CursorName<\/i> can be in any form accepted by Tk_GetCursor<\/b>. The default cursor is wait<\/b> on Windows and watch<\/b> on other platforms.<\/p>\n tk busy cget<\/b> window option<\/i><\/p>\n Queries the tk busy<\/b> command configuration options for window<\/i>. Window<\/i> must be the path name of a widget previously made busy by the hold<\/b> operation. The command returns the present value of the specified option<\/i>. Option<\/i> may have any of the values accepted by the hold<\/b> operation.<\/p>\n tk busy configure<\/b> window<\/i> ?option value<\/i>?…<\/p>\n Queries or modifies the tk busy<\/b> command configuration options for window<\/i>. Window<\/i> must be the path name of a widget previously made busy by the hold<\/b> operation. If no options are specified, a list describing all of the available options for window<\/i> (see Tk_ConfigureInfo<\/b> for information on the format of this list) is returned. If option<\/i> is specified with no value<\/i>, then the command returns a list describing the one named option (this list will be identical to the corresponding sublist of the value returned if no option<\/i> is specified). If one or more option\u2212value<\/i> pairs are specified, then the command modifies the given widget option(s) to have the given value(s); in this case the command returns the empty string. Option<\/i> may have any of the values accepted by the hold<\/b> operation.<\/p>\n Please note that the option database is referenced through window<\/i>. For example, if the widget .frame<\/b> is to be made busy, the busy cursor can be specified for it by either option<\/b> command:<\/p>\n option add *frame.busyCursor gumby tk busy forget<\/b> window<\/i> ?window<\/i>?…<\/p>\n Releases resources allocated by the tk busy<\/b> command for window<\/i>, including the transparent window. User events will again be received by window<\/i>. Resources are also released when window<\/i> is destroyed. Window<\/i> must be the name of a widget specified in the hold<\/b> operation, otherwise an error is reported.<\/p>\n tk busy current<\/b> ?pattern<\/i>?<\/p>\n Returns the pathnames of all widgets that are currently busy. If a pattern<\/i> is given, only the path names of busy widgets matching pattern<\/i> are returned.<\/p>\n tk busy status<\/b> window<\/i><\/p>\n Returns the status of a widget window<\/i>. If window<\/i> presently can not receive user interactions, 1<\/b> is returned, otherwise 0<\/b>.<\/p>\n BINDINGS<\/b> tk busy<\/b> hold .frame.canvas Normally the busy window is a sibling of the widget. The name of the busy window is \u201cwidget<\/i>_Busy<\/b>\u201d where widget<\/i> is the name of the widget to be made busy. In the previous example, the pathname of the busy window is \u201c.frame.canvas_Busy<\/b>\u201d. The exception is when the widget is a toplevel widget (such as \u201c.\u201d) where the busy window can\u2019t be made a sibling. The busy window is then a child of the widget named \u201cwidget<\/i>._Busy<\/b>\u201d where widget<\/i> is the name of the toplevel widget. In the following example, the pathname of the busy window is \u201c._Busy<\/b>\u201d.<\/p>\n tk busy<\/b> hold . ENTER\/LEAVE EVENTS<\/b> KEYBOARD EVENTS<\/b> pack [frame .frame] The above example moves the focus from .frame immediately after invoking the hold<\/b> so that no keyboard events will be sent to .frame<\/b> or any of its descendants. It also makes sure it\u2019s not possible to leave button .cancel<\/b> using the keyboard.<\/p>\n Note that the tk busy<\/b> command does not currently have any effect on OSX when Tk is built using Aqua support.<\/p>\n grab(n)<\/p>\n busy, keyboard events, pointer events, window<\/p>\n busy \u2212 confine pointer events to a window sub-tree <\/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":[2791,2635],"class_list":["post-6136","post","type-post","status-publish","format-standard","hentry","category-n-comandos-tcl-tk","category-sin-categoria","tag-busy","tag-mann"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6136","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=6136"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6136\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=6136"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=6136"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=6136"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
SYNOPSIS<\/a>
DESCRIPTION<\/a>
INTRODUCTION<\/a>
OPERATIONS<\/a>
EVENT HANDLING<\/a>
PORTABILITY<\/a>
SEE ALSO<\/a>
KEYWORDS<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
INTRODUCTION <\/a> <\/h2>\n
You can make several widgets busy by simply making its ancestor widget busy using the hold<\/b> operation.<\/p>\n
button .top.button; canvas .top.canvas
pack .top.button .top.canvas
pack .top
# . . .
tk busy<\/b> hold .top
update<\/p>\nOPERATIONS <\/a> <\/h2>\n
tk busy<\/b> window<\/i> ?option value<\/i>?…<\/p>\n
\u2212cursor<\/b> cursorName<\/i><\/p>\n
option add *Frame.BusyCursor gumby<\/p>\nEVENT HANDLING <\/a> <\/h2>\n
The event blocking feature is implemented by creating and mapping a transparent window that completely covers the widget. When the busy window is mapped, it invisibly shields the widget and its hierarchy from all events that may be sent. Like Tk widgets, busy windows have widget names in the Tk window hierarchy. This means that you can use the bind<\/b> command, to handle events in the busy window.<\/p>\n
bind .frame.canvas_Busy
bind ._Busy
Mapping and unmapping busy windows generates Enter\/Leave events for all widgets they cover. Please note this if you are tracking Enter\/Leave events in widgets.<\/p>\n
When a widget is made busy, the widget is prevented from gaining the keyboard focus by a user clicking on it by the busy window. But if the widget already had focus, it still may receive keyboard events. The widget can also still receive focus through keyboard traversal. To prevent this, you must move focus to another window and make sure the focus can not go back to the widgets made busy (e.g. but restricting focus to a cancel button).<\/p>\n
pack [text .frame.text]
tk busy<\/b> hold .frame
pack [button .cancel -text “Cancel” -command exit]
focus .cancel
bind .cancel
bind .cancel
update<\/p>\nPORTABILITY <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n
KEYWORDS <\/a> <\/h2>\n
\n","protected":false},"excerpt":{"rendered":"