Multi-event sequences and ignored events

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
  - Introduction
  - Event Patterns
  - Modifiers
  - Event Types
  - Substitutions
  - Multiple Matches
  - Multi-event
- 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

When a sequence specified in a tk/bind command contains more than one event pattern, then its script is executed whenever the recent events (leading up to and including the current event) match the given sequence.

This means, for example, that if button 1 is clicked repeatedly the sequence <Double-ButtonPress-1> will match each button press but the first.

If extraneous events that would prevent a match occur in the middle of an event sequence then the extraneous events are ignored unless they are KeyPress or ButtonPress events. For example, <Double-ButtonPress-1> will match a sequence of presses of button 1, even though there will be ButtonRelease events (and possibly Motion events) between the ButtonPress events.

Furthermore, a KeyPress event may be preceded by any number of other KeyPress events for modifier keys without the modifier keys preventing a match. For example, the event sequence aB will match a press of the a key, a release of the a key, a press of the Shift key, and a press of the b key: the press of Shift is ignored because it is a modifier key.

Finally, if several Motion events occur in a row, only the last one is used for purposes of matching binding sequences.


		Multi-event sequences and ignored events
		Multi-event sequences and ignored events

	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 Introduction Event Patterns Modifiers Event Types Substitutions Multiple Matches Multi-event 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	When a sequence specified in a `tk/bind` command contains more than one event pattern, then its script is executed whenever the recent events (leading up to and including the current event) match the given sequence. This means, for example, that if button 1 is clicked repeatedly the sequence `<Double-ButtonPress-1>` will match each button press but the first. If extraneous events that would prevent a match occur in the middle of an event sequence then the extraneous events are ignored unless they are KeyPress or ButtonPress events. For example, `<Double-ButtonPress-1>` will match a sequence of presses of button 1, even though there will be ButtonRelease events (and possibly Motion events) between the ButtonPress events. Furthermore, a KeyPress event may be preceded by any number of other KeyPress events for modifier keys without the modifier keys preventing a match. For example, the event sequence `aB` will match a press of the `a` key, a release of the `a` key, a press of the Shift key, and a press of the `b` key: the press of Shift is ignored because it is a modifier key. Finally, if several Motion events occur in a row, only the last one is used for purposes of matching binding sequences. © Author \| Home \| Sitemap