mouse driver and event

How does the mouse driver send information to Photon Manager? The following
should be made sure:
1.Which kinds of event does the mouse driver send?
2.Which functions of Netrino and Photon would be used to finish this
process?
3.Who are the emitter or collector of the mouse event?
4.What is the relationship between the mouse driver and mouse cursor?
Please show me some example about those. Thanks a lot!

jigang <jigang@jinglun.com.cn> wrote:

How does the mouse driver send information to Photon Manager? The following
should be made sure:

1.Which kinds of event does the mouse driver send?

PhEvent_t events

2.Which functions of Netrino and Photon would be used to finish this
process?

PhEventEmit

3.Who are the emitter or collector of the mouse event?

Your app is the emitter… the collector is whatever app is at the same
coordinates as the event you emitted.

4.What is the relationship between the mouse driver and mouse cursor?

There is no relationship. The mouse cursor’s position and shape are determined
by Photon… not the mouse driver.

Please show me some example about those. Thanks a lot!

When there is an input driver development kit ready, there will be examples
in it.

How can I get the input driver development kit ?

<pete@qnx.com> wrote in message news:8urj2i$2mu$2@nntp.qnx.com

jigang <> jigang@jinglun.com.cn> > wrote:
How does the mouse driver send information to Photon Manager? The
following
should be made sure:

1.Which kinds of event does the mouse driver send?

PhEvent_t events

2.Which functions of Netrino and Photon would be used to finish this
process?

PhEventEmit

3.Who are the emitter or collector of the mouse event?

Your app is the emitter… the collector is whatever app is at the same
coordinates as the event you emitted.

4.What is the relationship between the mouse driver and mouse cursor?

There is no relationship. The mouse cursor’s position and shape are
determined
by Photon… not the mouse driver.

Please show me some example about those. Thanks a lot!

When there is an input driver development kit ready, there will be
examples
in it.

<pete@qnx.com> wrote in message news:8urj2i$2mu$2@nntp.qnx.com

When there is an input driver development kit ready, there will be
examples
in it.

I can’t wait for this. I may need to write some custom digitizer drivers
(some are older Wacom, the one for the Compaq Concerto is unique to that
hardware AFAIK) that I doubt will be supported out of the box but for which
I have the complete hardware-level protocol specs (which IO port address &
interupt they are at if present, the format of the control packets and data
packets, etc) so I’m hoping it should be not terribly difficult to convert a
generic example driver to do the job…

Marisa

jigang <jigang@jinglun.com.cn> wrote:

How can I get the input driver development kit ?

When it’s available it will be in a public cvs repository that anyone
can get at.

Marisa Giancarla <mgiancarla@macromedia.com> wrote:

pete@qnx.com> > wrote in message news:8urj2i$2mu$> 2@nntp.qnx.com> …
When there is an input driver development kit ready, there will be
examples
in it.

I can’t wait for this.

OK… so what do you plan to do then?

I may need to write some custom digitizer drivers
(some are older Wacom, the one for the Compaq Concerto is unique to that
hardware AFAIK) that I doubt will be supported out of the box but for which
I have the complete hardware-level protocol specs (which IO port address &
interupt they are at if present, the format of the control packets and data
packets, etc) so I’m hoping it should be not terribly difficult to convert a
generic example driver to do the job…

It’s really too bad you can’t wait for the Input development kit. There will
be generic example drivers in it.

“Marisa Giancarla” <mgiancarla@macromedia.com> wrote in message
news:8usmkg$oat$1@inn.qnx.com

I can’t wait for this. I may need to write some custom digitizer drivers
(some are older Wacom, the one for the Compaq Concerto is unique to that
hardware AFAIK) that I doubt will be supported out of the box but for
which

Strange as it may seem, Input (for QNX4 anyway) does support Wacom ISD 3.0
and Compaq Concerto out-of-the-box. Not sure about RtP, but I would hope
that QSSL don’t drop support for anything that is currently supported on QNX
4 (although I wouldn’t expect oddballs to show up initially).

When is the input driver development kit available?
<pete@qnx.com> wrote in message news:8uule6$5ss$1@nntp.qnx.com

jigang <> jigang@jinglun.com.cn> > wrote:
How can I get the input driver development kit ?

When it’s available it will be in a public cvs repository that anyone
can get at.

jigang <jigang@jinglun.com.cn> wrote:

When is the input driver development kit available?

We are redoing the way input works, and we don’t want to encourage
a lot of people to write input drivers the way they work currently.

If you really need to do an input driver in the short term, you
should get in touch with your sales rep, sign an NDA, and we can give
you the current input driver libraries and some examples.

Otherwise, you’re probably looking at sometime first quarter next
year for a redesigned input with a publicly released input driver kit.

That was an “I’m so excited” meaning “I can’t wait”, not a “I’m giving up on
this” meaning… I’m working on other projects until the input driver SDK is
ready…

Marisa

“John Doe” <john@csical.com> wrote in message
news:8uv5ab$aem$1@inn.qnx.com

Strange as it may seem, Input (for QNX4 anyway) does support Wacom ISD
3.0
and Compaq Concerto out-of-the-box. Not sure about RtP, but I would hope
that QSSL don’t drop support for anything that is currently supported on
QNX
4 (although I wouldn’t expect oddballs to show up initially).

That will be great, if true. If I can just get over my chicken & egg
bootstraping issue and actually get RTP loaded on a system with no CD drive
I’ll be all set… I’m thinking of trying to use a Ricoh tablet which has a
(nonbootable) CD drive but no floppy since I have HD images with Win95 for
it and should then be able to use the RTP “boot from in windows” ability to
get it up enough to dinit a CF card and make a QNX boot image of my own on
it to use to bring the other systems up…

Marisa

Marisa Giancarla <mgiancarla@macromedia.com> wrote:

That was an “I’m so excited” meaning “I can’t wait”, not a “I’m giving up on
this” meaning… I’m working on other projects until the input driver SDK is
ready…

Ahhh… OK.

John Doe <john@csical.com> wrote:

“Marisa Giancarla” <> mgiancarla@macromedia.com> > wrote in message
news:8usmkg$oat$> 1@inn.qnx.com> …

Strange as it may seem, Input (for QNX4 anyway) does support Wacom ISD 3.0
and Compaq Concerto out-of-the-box. Not sure about RtP, but I would hope
that QSSL don’t drop support for anything that is currently supported on QNX
4 (although I wouldn’t expect oddballs to show up initially).

That’s already happened with some of the video drivers.