Page 196	Table of Contents	Index	Page 198
	Chapters
	1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 A, B, C, D, E

CHAPTER 22. EXTENDED STREAM INPUT

:pointer-motion or :timer.

As an example, the :edit gesture name above could be defined as follows using define-gesture- name:

 
 (define-gesture-name :edit :pointer-button (:left :meta))
 (define-gesture-name :edit :keyboard (#\E :control))

=> delete-gesture-name name [Function]
Removes the gesture named by the symbol name.

=> event-matches-gesture-name-p event gesture-name [Function]
Returns true if the device event event "matches" the gesture named by gesture-name.

For pointer button events, the event matches the gesture name when the pointer button from
the event matches the name of the pointer button one of the gesture specifications named by
gesture-name, and the modifier key state from the event matches the names of the modifier keys
in that same gesture specification.

For keyboard events, the event matches the gesture name when the key name from the event
matches the key name of one of the gesture specifications named by gesture-name, and the
modifier key state from the event matches the names of the modifier keys in that same gesture
specification.

=> modifier-state-matches-gesture-name-p modifier-state gesture-name [Function]
Returns true if the modifier key state from the device event event matches the names of the
modifier keys in one of the gesture specifications named by gesture-name.

Minor issue: Note that none of the functions above take a port argument. This is because
CLIM implicitly assumes that the canonical set of gesture names is the same on every port, and
only the mappings differ from port to port. Some ports may define additional gesture names,
but they will simply not be mapped on other ports. Is this a reasonable assumption? | SWM

22.3.1 Standard Gesture Names

Every CLIM implementation must provide a standard set of gesture names that correspond to
a common set of gestures. These gesture names must have a meaningful mapping for every port
type.

Here are the required, standard keyboard gesture names:

:abort - corresponds to gestures that cause the currently running application to be aborted
back to top-level. On Genera, this will match the #\Abort character. On other systems,
this may match the event corresponding to typing Control-C.

Page 196	Table of Contents	Index	Page 198
	Chapters
	1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 A, B, C, D, E