Artifact 8d228c31da60d849480bfc650bdf00d5d8d03f965c65385dd2c8c8c987c5f81d:

File tip/492.md — part of check-in [a3499f4937] at 2018-02-10 15:47:15 on branch trunk — Accepted 5/0/1: YES: 5 (Fellows, Ferrieux, Griffin, Landers, Vogel). NO: -. PRESENT: 1 (Kenny). Vote conclusion email was sent 10 Feb. 2018 to Tcl Core list. Implementation was merged same day. (user: fvogel size: 1552)

TIP 492: Introspection for 'tk busy'

Author:         Francois Vogel <[email protected]>
State:          Final
Type:           Project
Vote:           Done
Created:        19-Dec-2017
Post-History:
Keywords:       tk busy
Tcl-Version:    8.7

Abstract

This TIP provides user access to the busy window that Tk uses to let a user think a widget is busy.

Rationale

The tk::busy documentation describes how a busy window is created to block events. The path of this busy window can be used to handle some events. This path is dependent on whether the widget to be covered is a toplevel or not, see implementation details here and also the man page for tk busy.

As a consequence, this logic needs to be known by any user of the tk busy command. Offering a way to get the path of the busy window would avoid this dependency on the implementation details.

Proposal

It is proposed to:

Let the tk busy hold subcommand (and its shortcut tk busy) return the pathname of the busy window instead of the empty string.
Provide a new subcommand tk busy busywindow to return that same information, or the empty string if the windows passed to it is currently not busy.
Remove any mention of the details of the busy window naming from the man page.

Implementation

An implementation of this TIP can be found in the tip-492 branch.

Copyright

This document has been placed in the public domain.