tk/wm protocol
- Preface
- Introduction
- Tutorial
- Implementation
- Commands
- bitmap
- eval-wish
- get-tk-var
- photo
- set-tk-var!
- tk
- tk-id->widget
- tk-var
- tk/after
- tk/appname
- tk/bind
- tk/bindtags
- tk/caret
- tk/choosecolor
- tk/choosedirectory
- tk/clipboard
- tk/console
- tk/destroy
- tk/dialog
- tk/event
- tk/focus
- tk/getopenfile
- tk/getsavefile
- tk/grab
- tk/grid
- tk/image
- tk/lower
- tk/messagebox
- tk/option
- tk/pack
- tk/place
- tk/popup
- tk/raise
- tk/scaling
- tk/update
- tk/useinputmethods
- tk/wait
- tk/windowingsystem
- tk/winfo
- tk/wm
- Options
- Extensions
- Changes
- (tk/wm 'protocol #<widget> ?name? ?command?)
- This command is used to manage window manager protocols such as WM_DELETE_WINDOW. Name is the name of an atom corresponding to a window manager protocol, such as WM_DELETE_WINDOW or WM_SAVE_YOURSELF or WM_TAKE_FOCUS. If both name and command are specified, then command is associated with the protocol specified by name. Name will be added to #<widget>'s WM_PROTOCOLS property to tell the window manager that the application has a protocol handler for name, and command will be invoked in the future whenever the window manager sends a message to the client for that protocol. In this case the command returns an empty string. If name is specified but command isn't, then the current command for name is returned, or an empty string if there is no handler defined for name. If command is specified as an empty string then the current handler for name is deleted and it is removed from the WM_PROTOCOLS property on #<widget>; an empty string is returned. Lastly, if neither name nor command is specified, the command returns a list of all the protocols for which handlers are currently defined for #<widget>.
Tk always defines a protocol handler for WM_DELETE_WINDOW, even if you haven't asked for one with tk/wm protocol. If a WM_DELETE_WINDOW message arrives when you haven't defined a handler, then Tk handles the message by destroying the window for which it was received.