> - You could create an invisible button widget, and bind it to the
> hotkey. This would require almost no new code. (just a 'visible'
> property for widgets, which we need anyway) The widget would take
> a little more memory than the event filter idea above. It would
> also be a little less flexible: you could intercept a specified
> key, but couldn't do something more complex like a keyboard mapping.
>
This way works. Instead of making them invisible, I just made the button
have a size of zero. It doesn't seem to mess up the hotspot system (you
can't use the arrow keys to activate the invisible buttons). I've patched up
the input driver for the VR3 and tested the system out. I can now pop up the
soft keyboard (pgboard) by pressing on the VR3's little keyboard icon. Now I
need to fix up pgboard. It seems to be a bit broken at 160x240x4 graphics
mode.
Thanks for the suggestion,
-Sean
_______________________________________________
Pgui-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/pgui-devel
