Mercurial > hg > xemacs-beta
comparison src/dialog-x.c @ 185:3d6bfa290dbd r20-3b19
Import from CVS: tag r20-3b19
| author | cvs |
|---|---|
| date | Mon, 13 Aug 2007 09:55:28 +0200 |
| parents | 131b0175ea99 |
| children | 557eaa0339bf |
comparison
equal
deleted
inserted
replaced
| 184:bcd2674570bf | 185:3d6bfa290dbd |
|---|---|
| 221 | 221 |
| 222 The rest of the elements are descriptions of the dialog box's buttons. | 222 The rest of the elements are descriptions of the dialog box's buttons. |
| 223 Each of these is a vector, the syntax of which is essentially the same as | 223 Each of these is a vector, the syntax of which is essentially the same as |
| 224 that of popup menu items. They may have any of the following forms: | 224 that of popup menu items. They may have any of the following forms: |
| 225 | 225 |
| 226 [ \"name\" callback <active-p> ] | 226 [ "name" callback <active-p> ] |
| 227 [ \"name\" callback <active-p> \"suffix\" ] | 227 [ "name" callback <active-p> "suffix" ] |
| 228 [ \"name\" callback :<keyword> <value> :<keyword> <value> ... ] | 228 [ "name" callback :<keyword> <value> :<keyword> <value> ... ] |
| 229 | 229 |
| 230 The name is the string to display on the button; it is filtered through the | 230 The name is the string to display on the button; it is filtered through the |
| 231 resource database, so it is possible for resources to override what string | 231 resource database, so it is possible for resources to override what string |
| 232 is actually displayed. | 232 is actually displayed. |
| 233 | 233 |
| 236 evaluated with `eval'. | 236 evaluated with `eval'. |
| 237 | 237 |
| 238 One (and only one) of the buttons may be `nil'. This marker means that all | 238 One (and only one) of the buttons may be `nil'. This marker means that all |
| 239 following buttons should be flushright instead of flushleft. | 239 following buttons should be flushright instead of flushleft. |
| 240 | 240 |
| 241 Though the keyword/value syntax is supported for dialog boxes just as in | 241 Though the keyword/value syntax is supported for dialog boxes just as in |
| 242 popup menus, the only keyword which is both meaningful and fully implemented | 242 popup menus, the only keyword which is both meaningful and fully implemented |
| 243 for dialog box buttons is `:active'. | 243 for dialog box buttons is `:active'. |
| 244 */ | 244 */ |
| 245 (dbox_desc)) | 245 (dbox_desc)) |
| 246 { | 246 { |
| 275 command (bound to the button-click) simply pops up the dialog, | 275 command (bound to the button-click) simply pops up the dialog, |
| 276 and returns. This causes a sequence of magic-events (destined | 276 and returns. This causes a sequence of magic-events (destined |
| 277 for the dialog widget) to begin. Eventually, a dialog item is | 277 for the dialog widget) to begin. Eventually, a dialog item is |
| 278 selected, and a misc-user-event blip is pushed onto the end of | 278 selected, and a misc-user-event blip is pushed onto the end of |
| 279 the input stream, which is then executed by the event loop. | 279 the input stream, which is then executed by the event loop. |
| 280 | 280 |
| 281 So there are two command-events, with a bunch of magic-events | 281 So there are two command-events, with a bunch of magic-events |
| 282 between them. We don't want the *first* command event to alter | 282 between them. We don't want the *first* command event to alter |
| 283 the state of the region, so that the region can be available as | 283 the state of the region, so that the region can be available as |
| 284 an argument for the second command. */ | 284 an argument for the second command. */ |
| 285 if (zmacs_regions) | 285 if (zmacs_regions) |