comparison: doc/TCL-HOWTO.dox
doc/TCL-HOWTO.dox
- branch
- next.minor
- changeset 25889
- 26d9ca30335c
- parent 24595
- 8b5abc3f53a9
- child 26824
- c7ba07f9ca42
equal
deleted
inserted
replaced
| 25888:d0fdd378a635 | 25889:26d9ca30335c |
|---|---|
| 330 intended to be a list only of their arguments. Signal callbacks will | 330 intended to be a list only of their arguments. Signal callbacks will |
| 331 be made in their own namespace, and arguments to those signal | 331 be made in their own namespace, and arguments to those signal |
| 332 callbacks will live in the namespace @c event underneath that | 332 callbacks will live in the namespace @c event underneath that |
| 333 namespace. To briefly illustrate, the signal @c receiving-im-msg is | 333 namespace. To briefly illustrate, the signal @c receiving-im-msg is |
| 334 provided with three arguments; the account on which the IM was | 334 provided with three arguments; the account on which the IM was |
| 335 received, the screen name of the user sending the IM, and the text of | 335 received, the name of the buddy sending the IM, and the text of |
| 336 the IM. These arguments live in the variables @c event::account, | 336 the IM. These arguments live in the variables @c event::account, |
| 337 @c event::sender, and @c event::buffer, respectively. Therefore a callback | 337 @c event::sender, and @c event::buffer, respectively. Therefore a callback |
| 338 which notifies the user of an incoming IM containing the word 'shizzle' | 338 which notifies the user of an incoming IM containing the word 'shizzle' |
| 339 might look like this: | 339 might look like this: |
| 340 | 340 |
