summaryrefslogtreecommitdiffstats
path: root/tcllib/modules/uev/uevent.man
blob: a10dffc504da22b6acf76df44aaeb10f4e461c24 (plain)
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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
[manpage_begin uevent n 0.3.1]
[see_also hook(n)]
[keywords bind]
[keywords event]
[keywords {generate event}]
[keywords hook]
[keywords unbind]
[copyright {2007-2012 Andreas Kupries <andreas_kupries@users.sourceforge.net>}]
[moddesc   {User events}]
[titledesc {User events}]
[category  {Programming tools}]
[require Tcl 8.4]
[require uevent [opt 0.3.1]]
[require logger]
[description]

This package provides a general facility for the handling of user
events. Allows the binding of arbitrary commands to arbitrary events
on arbitrary tags, removal of bindings, and event generation.

[para]

The main difference to the event system built into the Tcl/Tk core is
that the latter can generate only virtual events, and only for
widgets. It is not possible to use the builtin facilities to bind to
events on arbitrary (pseudo-)objects, nor is it able to generate
events for such.

[para]

Here we can, by assuming that each object in question is represented
by its own tag. Which is possible as we allow arbitrary tags.

[para]

More differences:

[list_begin enumerated]
[enum]

The package uses only a two-level hierarchy, tags and events, to
handle everything, whereas the Tcl/Tk system uses three levels, i.e.
objects, tags, and events, with a n:m relationship between objects and
tags.

[enum]
This package triggers all bound commands for a tag/event combination,
and they are independent of each other. A bound command cannot force
the event processing core to abort the processing of command coming
after it.

[list_end]

[section API]

The package exports eight commands, as specified below. Note that when
the package is used from within Tcl 8.5+ all the higher commands are
ensembles, i.e. the :: separators can be replaceed by spaces.

[list_begin definitions]
[comment ============================================================]
[call [cmd ::uevent::bind] [arg tag] [arg event] [arg command]]

Using this command registers the [arg command] prefix to be triggered
when the [arg event] occurs for the [arg tag]. The result of the
command is an opaque token representing the binding. Note that if the
same combination of <[arg tag],[arg event],[arg command]> is used
multiple times the same token is returned by every call.

[para]

The signature of the [arg command] prefix is

[list_begin definitions]
[call [cmd command] [arg tag] [arg event] [arg details]]
[list_end]
[para]

where [arg details] contains the argument(s) of the event. Its
contents are event specific and have to be agreed upon between actual
event generator and consumer. This package simply transfers the
information and does not perform any processing beyond that.

[comment ============================================================]
[call [cmd ::uevent::unbind] [arg token]]

This command releases the event binding represented by the
[arg token]. The token has to be the result of a call to
[cmd ::uevent::bind]. The result of the command is the empty string.

[comment ============================================================]
[call [cmd ::uevent::generate] [arg tag] [arg event] [opt [arg details]]]

This command generates an [arg event] for the [arg tag], triggering
all commands bound to that combination. The [arg details] argument is
simply passed unchanged to all event handlers. It is the
responsibility of the code generating and consuming the event to have
an agreement about the format and contents of the information carried
therein. The result of the command is the empty string.

[para]

Note that all bound commands are triggered, independently of each
other. The event handlers cannot assume a specific order. They are
also [emph not] called synchronously with the invokation of this
command, but simply put into the event queue for processing when the
system returns to the event loop.

[para]

Generating an event for an unknown tag, or for a
<[arg tag],[arg event]> combination which has no commands bound to it
is allowed, such calls will be ignored.

[comment ============================================================]
[call [cmd ::uevent::list]]

In this form the command returns a list containing the names of all
tags which have events with commands bound to them.

[comment ============================================================]
[call [cmd ::uevent::list] [arg tag]]

In this format the command returns a list containing the names of all
events for the [arg tag] with commands bound to them. Specifying an
unknown tag, i.e. a tag without event and commands, will cause the
command to throw an error.

[comment ============================================================]
[call [cmd ::uevent::list] [arg tag] [arg event]]

In this format the command returns a list containing all commands
bound to the [arg event] for the [arg tag]. Specifying an unknown tag
or unknown event, will cause the command to throw an error.

[comment ============================================================]
[call [cmd ::uevent::watch::tag::add] [arg pattern] [arg command]]

This command sets up a sort of reverse events. Events generated,
i.e. the [arg command] prefix invoked, when observers bind to and
unbind from specific tags.

[para] Note that the command prefix is only invoked twice per tag,
first when the first command is bound to any event of the tag, and
second when the last command bound to the tag is removed.

[para] The signature of the [arg command] prefix is

[list_begin definitions]
[call [cmd "{*}command"] [const bound]   [arg tag]]
[call [cmd "{*}command"] [const unbound] [arg tag]]
[list_end]

[para] The result of the command is a token representing the watcher.

[comment ============================================================]
[call [cmd ::uevent::watch::tag::remove] [arg token]]

This command removes a watcher for (un)bind events on tags.

[para] The result of the command is the empty string.

[comment ============================================================]
[call [cmd ::uevent::watch::event::add] [arg tag_pattern] [arg event_pattern] [arg command]]

This command sets up a sort of reverse events. Events generated,
i.e. the [arg command] prefix invoked, when observers bind to and
unbind from specific combinations of tags and events.

[para] Note that the command prefix is only invoked twice per
tag/event combination, first when the first command is bound to it,
and second when the last command bound to the it is removed.

[para] The signature of the [arg command] prefix is

[list_begin definitions]
[call [cmd "{*}command"] [const bound]   [arg tag] [arg event]]
[call [cmd "{*}command"] [const unbound] [arg tag] [arg event]]
[list_end]

[para] The result of the command is a token representing the watcher.

[comment ============================================================]
[call [cmd ::uevent::watch::event::remove] [arg token]]

This command removes a watcher for (un)bind events on tag/event
combinations.

[para] The result of the command is the empty string.

[comment ============================================================]
[list_end]

[vset CATEGORY uevent]
[include ../doctools2base/include/feedback.inc]
[manpage_end]