Mercurial > hg > xemacs-beta
view etc/toolbar/printer-up.xpm @ 4780:2fd201d73a92
Call character_to_event on characters received from XIM, event-Xt.c
src/ChangeLog addition:
2009-12-17 Aidan Kehoe <kehoea@parhasard.net>
* events.h (character_to_event_meta_behavior): New enumeration,
describing what character_to_event should do with characters in
the range ?\x80-?\xFF, and passed as the third argument to
character_to_event instead of the binary use_console_meta_flag.
* events.c (character_to_event, Fcharacter_to_event):
* event-unixoid.c (read_event_from_tty_or_stream_desc):
* event-stream.c (maybe_kbd_translate, maybe_kbd_translate):
* event-msw.c (mswindows_need_event):
Use the new enumeration.
* event-Xt.c (x_to_emacs_keysym):
Call character_to_event when we receive XLookupChars events,
passing latin_1_maps_to_itself as the meta_behavior flag,
addressing the problem FKtPp sees in 87bpi9mwpu.fsf@yahoo.com.cn
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Thu, 17 Dec 2009 17:51:38 +0000 |
| parents | 376386a54a3c |
| children | 7910031dd78a |
line wrap: on
line source
/* XPM */ static char * printer[] = { "28 28 6 1", "X c Gray75 s backgroundToolBarColor", "o c black", "O c white", "+ c Gray60", "@ c Gray90", "# c Gray40", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXoooooooooXXXXXXXXXXXXX", "XXXXXXoOOOOOOOooXXXXXXXXXXXX", "XXXXXXoOooooOOoXoXXXXXXXXXXX", "XXXXXXoOOOOOOOoooooooXXXXXXX", "XXXXXXoOoooOOOOOOoXo+ooXXXXX", "XXXXXXoOOOOOOOOOOoo++++oXXXX", "XXXXXXoooooooooooo++++ooXXXX", "XXXXXo@@@@@@@@@@@o+++o+oXXXX", "XXXXo@@@@@@@@@@@@@o+o++oXXXX", "XXXooooooooooooooooo+++oXXXX", "XXXo@@@@@@@@@@@@@@@o+++oXXXX", "XXXo@@@@@@@@@@@@@@@o++ooXXXX", "XXXo@@@@@@@@@@@@@@@o+ooXXXXX", "XXXo@@@@@@@@@@@@@@@oo#oXXXXX", "XXXooooooooooooooooo#oXXXXXX", "XXXXo+++++++++++++o#oXXXXXXX", "XXXXXo+++++++++++o#oXXXXXXXX", "XXXXXo+++++++++++ooXXXXXXXXX", "XXXXXXooooooooooooXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};