Is it possible to use the wheel mouse to scroll up/down the window contents
under QNX 6.0.C environment ?
I picked up the Input SDK and USB DDK (might be beta). Based on them, I
modified the devu-mouse to convert the USB wheel data to the Microsoft wheel
mouse data structure, modified the devi-hirun to add some printf statement
for debugging. I tested these modules with a USB wheel mouse on QNX 6.0.C.
It seems that the devu-mouse can correctly handle the USB wheel data. Also,
it seems the devi-hirun can correctly make the mp structure which contains a
PTR_Z_DATA flag and a dz value. But I could not scroll up/down the window
contents, e.g. Voyager browser.
Kazz
Hi Kazz,
Hmmmm I would imagine that you would have to send PgUp/PgDw region calls
to the apps. I would ask in the RTP Photon news groups for something like
this.
Erick.
Kazz Yokomizo <yokomizo@mx3.ttcn.ne.jp> wrote:
Is it possible to use the wheel mouse to scroll up/down the window contents
under QNX 6.0.C environment ?
I picked up the Input SDK and USB DDK (might be beta). Based on them, I
modified the devu-mouse to convert the USB wheel data to the Microsoft wheel
mouse data structure, modified the devi-hirun to add some printf statement
for debugging. I tested these modules with a USB wheel mouse on QNX 6.0.C.
It seems that the devu-mouse can correctly handle the USB wheel data. Also,
it seems the devi-hirun can correctly make the mp structure which contains a
PTR_Z_DATA flag and a dz value. But I could not scroll up/down the window
contents, e.g. Voyager browser.
Kazz
Thank you for your support.
I could use the USB wheel mouse after starting the devi-hirun with the “kbd”
option. My test environment had both PS/2 keyboard/mouse and USB wheel
mouse. There were two devi-hirun running. I started the second devi-hirun
with only “msoft” option to test my USB mouse driver.
The devi-hirun for USB mouse must be required keyboard event bus line,
because the PgUp/PgDn key (scancode) is generated by devi-hirun to emulate
the wheel operation. The PgUp/PgDn scancodes might be sent to Photon using
the keyboard event bus line.
I think the current implementation might cause any problem on the form which
allows the cursor movements between input fields using PgUp/PgDn keys (not
Tab keys). In the Terminal application, we can see the problem easier when
using the mouse wheel.
Can I expect that the GA version of USB DDK contains the other solution for
the wheel operation than the PgUp/PgDn emulation ?
Kazz
“Hardware Support Account” <hw@qnx.com> wrote in message
news:9g69om$kvt$2@nntp.qnx.com…
Hi Kazz,
Hmmmm I would imagine that you would have to send PgUp/PgDw region calls
to the apps. I would ask in the RTP Photon news groups for something like
this.
Erick.
Kazz Yokomizo <> yokomizo@mx3.ttcn.ne.jp> > wrote:
Is it possible to use the wheel mouse to scroll up/down the window
contents
under QNX 6.0.C environment ?
I picked up the Input SDK and USB DDK (might be beta). Based on them, I
modified the devu-mouse to convert the USB wheel data to the Microsoft
wheel
mouse data structure, modified the devi-hirun to add some printf
statement
for debugging. I tested these modules with a USB wheel mouse on QNX
6.0.C.
It seems that the devu-mouse can correctly handle the USB wheel data.
Also,
it seems the devi-hirun can correctly make the mp structure which
contains a
PTR_Z_DATA flag and a dz value. But I could not scroll up/down the
window
contents, e.g. Voyager browser.
Kazz
Actually this is not correct.
Wheel behavior is controlled in input driver in the following ways.
- For applications that currently don’t process specially wheel activity,
driver sends KEY_UP/KEY_DOWN (PG_UP/PG_DOWN) keyboard events (the first
group - by default).
- If application is going to process wheel events itself, it can use dz
item of pointer event packet which driver sends to Photon… Unfortunately, I
cannot explain you how in this case to extract wheel movement information
from the corresponding Photon (Pointer) event.
- At least now, you can control this behavior using devctrl mechanism
(DEVCTL_SETZMODE).
“Kazz Yokomizo” <yokomizo@mx3.ttcn.ne.jp> wrote in message
news:9gpvs5$mn$1@nntp.qnx.com…
Thank you for your support.
I could use the USB wheel mouse after starting the devi-hirun with the
“kbd”
option. My test environment had both PS/2 keyboard/mouse and USB wheel
mouse. There were two devi-hirun running. I started the second
devi-hirun
with only “msoft” option to test my USB mouse driver.
The devi-hirun for USB mouse must be required keyboard event bus line,
because the PgUp/PgDn key (scancode) is generated by devi-hirun to emulate
the wheel operation. The PgUp/PgDn scancodes might be sent to Photon
using
the keyboard event bus line.
I think the current implementation might cause any problem on the form
which
allows the cursor movements between input fields using PgUp/PgDn keys (not
Tab keys). In the Terminal application, we can see the problem easier
when
using the mouse wheel.
Can I expect that the GA version of USB DDK contains the other solution
for
the wheel operation than the PgUp/PgDn emulation ?
Kazz
“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9g69om$kvt$> 2@nntp.qnx.com> …
Hi Kazz,
Hmmmm I would imagine that you would have to send PgUp/PgDw region calls
to the apps. I would ask in the RTP Photon news groups for something
like
this.
Erick.
Kazz Yokomizo <> yokomizo@mx3.ttcn.ne.jp> > wrote:
Is it possible to use the wheel mouse to scroll up/down the window
contents
under QNX 6.0.C environment ?
I picked up the Input SDK and USB DDK (might be beta). Based on them,
I
modified the devu-mouse to convert the USB wheel data to the Microsoft
wheel
mouse data structure, modified the devi-hirun to add some printf
statement
for debugging. I tested these modules with a USB wheel mouse on QNX
6.0.C.
It seems that the devu-mouse can correctly handle the USB wheel data.
Also,
it seems the devi-hirun can correctly make the mp structure which
contains a
PTR_Z_DATA flag and a dz value. But I could not scroll up/down the
window
contents, e.g. Voyager browser.
Kazz