Hi all. A simple solution was found :) I hacked the "KP_Prior" and "KP_Next" keys, and now they are used for making-window-smaller and restoring-original-window-size respectively :) All thanks to * /usr/share/X11/xkb/keycodes/evdev * sugar/src/jarabe/view/keyhandler.py Just one thing I noticed when I tried to have the above keys take effect ONLY in ebook-mode (via the "evtest --query" test), that when I ran this again and again via the "suprocess" module, the XO-4 behaved very erratically. However, when I made the keys take effect irrespective of the test of ebook-mode, things worked cool. However, I will keep on looking into the reason. Thanks a ton to all :) <div class="gmail_quote">On Thu, Jan 24, 2013 at 10:45 PM, Paul Fox <<a href="mailto:pgf@laptop.org" target="_blank">pgf@laptop.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">gonzalo wrote: > Write does not know what is the ebook switch state, that logic is in the > osk. > > Looking in the wiki and sugar code, I could not find information about how > read the switch, > but in ticket <a href="http://dev.laptop.org/ticket/12326" target="_blank">http://dev.laptop.org/ticket/12326</a> found this: > > If you do: > > evtest --query /dev/input/event4 EV_SW SW_TABLET_MODE; echo $? > > > If the xo is in ebook mode returns 10, if not, returns 0. > > There are any official doc about the switches I am missing? There are a way > to catch a event when the switch is activated, using dbus or something > similar? </div>if you open the device and read it, you'll get a stream of "struct input_event" structures (/usr/include/linux/input.h) representing opening and closing of the SW_TABLET_MODE switch. here's a C code snippet from olpc-switchd (part of powerd): void ebook_event() { struct input_event ev[1]; if (read(ebk_fd, ev, sizeof(ev)) != sizeof(ev)) die("bad read from ebook switch"); dbg(3, "ebk: ev sec %d usec %d type %d code %d value %d", ev->time.tv_sec, ev->time.tv_usec, ev->type, ev->code, ev->value); if (ev->type == EV_SW && ev->code == SW_TABLET_MODE) { if (ev->value) send_event("ebookclose", round_secs(ev), ebk_device); else send_event("ebookopen", round_secs(ev), ebk_device); } } perhaps there's an evdev to dbus gateway of some sort, but i don't know about it, if so. the "evtest" commandline example, above, uses an ioctl on the input device to determine current state. here's snippet from the evtest source: (full source: git://<a href="http://anongit.freedesktop.org/evtest" target="_blank">anongit.freedesktop.org/evtest</a>) static int query_device(const char *device, const struct query_mode *query_mode> { int fd; int r; unsigned long state[NBITS(query_mode->max)]; fd = open(device, O_RDONLY); if (fd < 0) { perror("open"); return EXIT_FAILURE; } memset(state, 0, sizeof(state)); r = ioctl(fd, query_mode->rq, state); close(fd); if (r == -1) { perror("ioctl"); return EXIT_FAILURE; } if (test_bit(keycode, state)) return 10; /* different from EXIT_FAILURE */ else return 0; } paul <div class="im HOEnZb"> > > Gonzalo > > > On Thu, Jan 24, 2013 at 12:16 PM, Martin Langhoff <<a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a> > > wrote: > > > On Thu, Jan 24, 2013 at 10:13 AM, Paul Fox <<a href="mailto:pgf@laptop.org">pgf@laptop.org</a>> wrote: > > > i believe sugar already has code to detect the two modes, since > > > that's how it knows whether to present the OSK or not. > > > > Yep. Ajay, I think Write shows you the way :-) > > > > > > > > > > m > > -- > > <a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a> > > <a href="mailto:martin@laptop.org">martin@laptop.org</a> -- Software Architect - OLPC > > - ask interesting questions > > - don't get distracted with shiny stuff - working code first > > - <a href="http://wiki.laptop.org/go/User:Martinlanghoff" target="_blank">http://wiki.laptop.org/go/User:Martinlanghoff</a> > > </div><div class="HOEnZb"><div class="h5">=--------------------- paul fox, <a href="mailto:pgf@laptop.org">pgf@laptop.org</a> _______________________________________________ Devel mailing list <a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a> <a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a> </div></div></blockquote></div> -- Regards, Ajay Garg Dextrose Developer Activity Central: <a href="http://activitycentral.com/" style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)" target="_blank">http://activitycentral.com</a>