On 12/22/05, spike grobstein <[EMAIL PROTECTED]> wrote: > that doesn't seem to be working properly. it works for me.
> I've got an HBox filled with buttons and I'm trying to use the joystick to go > back and forth across the list. perhaps you need tab and not up arrow > i got it working last night, actually, although I wasn't aware of gtk.keysym. > apparently, that's only mentioned once on pygtk.org in an example. I had to > use the interactive prompt and help(gtk.keysym) to get info in it. yeah bugreport docs to include stuff about it in gtk contants if they don't > your example will work if I set a hardware_keycode in addition to the keyval. > I'm not overly excited about hard-coding numbers in like that, in case > something changes or some foreign keyboard layout is different and it winds > up screwing up. yea hw_code should not be used. perhpas you should consider using modifiers I don't know exactly why it doens't work 4 u though > is there something similar to keysym for finding hardware_keycode? don't use hw_Code > also, is there any way of specifying where in the widget hierarchy to start > the key-pressed-event? I'd rather have some control over where the spoofed > keypresses go so I can possibly do some filtering of them. not sure what u mean, but in most cases it's from inside to outside and with keypress this is the thing -- Nikos Kouremenos | Jabber ID: [EMAIL PROTECTED] | http://members.hellug.gr/nkour
_______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
