On Mon, 15 Dec 2008 19:11:03 +0100, "Kim Woelders" <[email protected]> wrote:
> On Mon, 15 Dec 2008 18:52:47 +0100, Dennis Nezic > <[email protected]> wrote: > > > On Sun, 14 Dec 2008 17:20:40 +0100, "Kim Woelders" <[email protected]> > > wrote: > > > >> On Sat, 13 Dec 2008 17:27:21 +0100, Dennis Nezic > >> <[email protected]> wrote: > >> > >> > On Wed, 10 Dec 2008 19:44:23 +0100, "Kim Woelders" > >> > <[email protected]> wrote: > >> > > >> >> On Tue, 09 Dec 2008 21:54:07 +0100, Dennis Nezic > >> >> <[email protected]> wrote: > >> >> > >> >> > I posted a couple of months ago about this issue (end of > >> >> > august), and still haven't managed to resolve it :P. So, to > >> >> > recap: > >> >> > > >> >> > * No keybindings of "special keys" work on my acer laptop > >> >> > keyboard (Option "XkbModel" "acer_ferrari4k") like XF86Mail, > >> >> > EuroSign, when e16 FIRST starts up--but they do with 'eesh > >> >> > restart'. This suggests that the problem is not with my > >> >> > configuration, but with the way e16 "grabs" control of the > >> >> > keyboard; perhaps a timing issue. Keybindings of "normal" keys > >> >> > always work. It should be noted that the special keys are > >> >> > recognized (xev)--just not bound. > >> >> > > >> >> > * An interesting anomaly is the normal 'dollar' symbol. My > >> >> > laptop has another separate key just for it, in addition to > >> >> > the normal one above the '4' key. But if I make a keybinding > >> >> > to 'dollar', it will trigger when I press '4' (not Shift-4). > >> >> > This problem of having the "shift-level" symbol being > >> >> > interpreted as the "first level" only exists with this > >> >> > duplicated dollar symbol, and not with others like 'at' or > >> >> > 'numbersign'. If I remove 'dollar' from my bindings.cfg, the > >> >> > '4' key is once again interpreted as '4', and not the > >> >> > key-bound dollar, which suggests that the problem has > >> >> > something to do with e16's key binding mechanism. > >> >> > > >> >> > * Most interesting of all, starting e16 with null theme > >> >> > (removing the theme folders; eesh theme says Name: (null)) > >> >> > makes the "special key" bindings work! This suggests that the > >> >> > bug has something to do with e16--even though it was only > >> >> > when I upgraded X (or one of X's keyboard modules) that the > >> >> > problem started. How can the keybinding process possibly > >> >> > differ if no theme is present versus if a theme is loaded?? > >> >> > > >> >> Timing? > >> >> Don't you get the "...mostly pointless..." screen where you > >> >> have to confirm? > >> >> Btw. as of 0.16.8.14 (IIRC) you can run "without" a theme using > >> >> option "-t -" (i.e. no need to trash the theme directories). > >> > > >> > > >> > Hmmmm.... actually, I have just discovered that it was not > >> > loading e16 with no theme that made the bindings work, but > >> > rather pressing F1 in the "mostly pointless" dialogue! If I used > >> > the mouse instead, the bindings wouldn't work--even with null > >> > theme! Further testing revealed that if I pressed random buttons > >> > on my keyboard while X/e16 was loading, the bindings would work! > >> > > >> > It does sound like something wrong with the "new X-server hotplug > >> > stuff" that you mention below--but specifically with e16, since > >> > the keys are properly mapped with their special layout > >> > symbols--they just aren't binded in e16--that is, only the > >> > special keys aren't binded... all the normal keys are. > >> > > >> > > >> >> > In other words, there's something about having no theme, or > >> >> > restarting e16, that makes things work--or something about > >> >> > initially loading a theme that breaks key bindings. I don't > >> >> > know enough about X or e16 keybinding internals to put all > >> >> > these pieces of the puzzle together. Hopefully someone else > >> >> > might? > >> >> > > >> >> Could it be something with keyboard mapping changing during > >> >> startup, maybe related to the new X-server hotplug stuff? > >> >> You could try adding a delay between starting the server and > >> >> starting e16, e.g. add "sleep 2" in some startup script. > >> > > >> > Sleeping doesn't help. (Although if I could somehow simulate a > >> > special keypress :/---but that is an ugly solution.) > >> > > >> Here's another hack that might fix things: > >> > >> Enable the session scripts: > >> $ eesh set misc.session.enable_script 1 > >> > >> Add a script (e.g. ~/.e16/Init/reload_bindings) to reload the > >> keybindings some time after startup: > >> #!/bin/sh > >> sleep 2 > >> eesh ac load bindings.cfg > > > > Interesting. That sortof works--but not really. When I run that > > command, in a startup script or later during the session, I get an > > "ActionClass Error!" popup dialog window with messages like "5 > > references remain". So I have to run it again, and usually I get the > > same error message but with a smaller value, like "1 references > > remain". The numbers don't appear fixed. I've seen "14 references > > remain", "4 references remain". > > > Yeah, I saw that. Should be fixed in svn. But doesn't it do the > trick? As far as I can tell the message is in this case only an > annoyance. No--it actually doesn't work. So long as I don't press anything on my keyboard, regardless if I issue that eesh ac load command, regardless how many times, or how many sleep delays I put in between them, e16 won't bind to the special keys. But, if I press any key, and /then/ issue the load command, or eesh restart, they are bound. The latest svn version, 15-0.01, does get rid of that ActionClass Error, but besides that, the same problem exists. Maybe we could add some debugging output to print what keyboard layout e16 thinks is being used? 'Cuz xev shows that the special keys are mapped properly--though, of course, it is necessary for me to type stuff first to get them--so maybe, just maybe, the layout isn't explicitly known to X until a key is pressed? Or maybe it's just a bug in e16? :) ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
