On Tue, Jun 18, 2002 at 09:34:19AM -0300, Lalo Martins wrote:
> On Sat, May 25, 2002 at 02:46:20PM -0600, Micah Dowty wrote:
> > For a relatively small number of keys, like the VR3 silkscreen buttons, you can
>use button hotkeys. Create a button widget for each silkscreen button, and assign
>PG_
On Sat, May 25, 2002 at 02:46:20PM -0600, Micah Dowty wrote:
> For a relatively small number of keys, like the VR3 silkscreen buttons, you can use
>button hotkeys. Create a button widget for each silkscreen button, and assign
>PG_WP_HOTKEY on the button to the PGKEY_* constant for the button. Th
The current driver just maps the soft buttons to F1 through F7.. there's no hardware
button support yet. If there's a way to get hardware button events from the kernel, it
could be added to the vr3ts driver.
On Sat, May 25, 2002 at 06:22:54PM -0300, Lalo Martins wrote:
> On Sat, May 25, 2002 at
On Sat, May 25, 2002 at 09:39:53PM +0100, James Hollingshead wrote:
>
> The reason for this is to try and use the silkscreen keys of the vr3ts
> input driver to pop up a window/menu/keyboard. The silkscreen keys
> appear to produce keyboard codes, so I want a (preferably unmapped)
> app that can
For a relatively small number of keys, like the VR3 silkscreen buttons, you can use
button hotkeys. Create a button widget for each silkscreen button, and assign
PG_WP_HOTKEY on the button to the PGKEY_* constant for the button. The button will
recieve that key's events. It can be unattached to
