input drivers?

Hi there, I’m a little unclear if this is the best forum for this
since the questions are all over the place, but at least it has photon
in the title :slight_smile:.

The photon docs mention ‘writing an input driver’ every once in a
while, but there isn’t really any mention of how one goes about
attaching it to the system (sort of the equivilant of how resource
managers export their existance via paths). I’ve got all the low-level
stuff happy talking through my resource manager, but would like for
photon apps to see things like button presses etc.

Any pointers? (It is highly likely that I just missed it since I’m
coming up to speed w/ neutrino at the same time, and don’t know the
right ‘words’ for everything yet).

\p

A person who hesitates is not only lost, but miles from the next exit.
— Richard Chou

d p chang <dpc@wintermute.redjade.com> wrote:

Hi there, I’m a little unclear if this is the best forum for this
since the questions are all over the place, but at least it has photon
in the title > :slight_smile:> .

The photon docs mention ‘writing an input driver’ every once in a
while, but there isn’t really any mention of how one goes about
attaching it to the system (sort of the equivilant of how resource
managers export their existance via paths). I’ve got all the low-level
stuff happy talking through my resource manager, but would like for
photon apps to see things like button presses etc.

Any pointers? (It is highly likely that I just missed it since I’m
coming up to speed w/ neutrino at the same time, and don’t know the
right ‘words’ for everything yet).

The SDK for writing input drivers under RTP is not ready for public
release yet.

In the meantime, read the programmers guide-> events section of the Photon
manual.

pete@qnx.com wrote:

d p chang <> dpc@wintermute.redjade.com> > wrote:
Hi there, I’m a little unclear if this is the best forum for this
since the questions are all over the place, but at least it has photon
in the title > :slight_smile:> .

The photon docs mention ‘writing an input driver’ every once in a
while, but there isn’t really any mention of how one goes about
attaching it to the system (sort of the equivilant of how resource
managers export their existance via paths). I’ve got all the low-level
stuff happy talking through my resource manager, but would like for
photon apps to see things like button presses etc.

Any pointers? (It is highly likely that I just missed it since I’m
coming up to speed w/ neutrino at the same time, and don’t know the
right ‘words’ for everything yet).

The SDK for writing input drivers under RTP is not ready for public
release yet.

It might be worth mentioning that the SDK is not really necessary to
build an input driver – it just makes typical things easier. A Photon
input driver is just an application that emits Photon input events (and
typically doesn’t display anything).

In the meantime, read the programmers guide-> events section of the Photon
manual.

If you want to write an input driver without waiting for the SDK, look
at the the several paragraphs that explains how to set up the region to
emit raw events from (the third bullet in the “Emitting key events”
section). It is rather vague and you’ll need to search header files for
details, but at least it will point you in the right direction.

But since this is rather low-level stuff, I don’t think it’s a good idea
for your first Photon project…


Wojtek Lerch (wojtek@qnx.com) QNX Software Systems Ltd.

Wojtek Lerch <wojtek@qnx.com> writes:

It might be worth mentioning that the SDK is not really necessary to
build an input driver – it just makes typical things easier. A
Photon input driver is just an application that emits Photon input
events (and typically doesn’t display anything).

This is what I was looking for

In the meantime, read the programmers guide-> events section of the Photon
manual.

If you want to write an input driver without waiting for the SDK, look
at the the several paragraphs that explains how to set up the region to
emit raw events from (the third bullet in the “Emitting key events”
section). It is rather vague and you’ll need to search header files for
details, but at least it will point you in the right direction.

I found this and something on the support page for emitting raw
events. I’m still playing around w/ all of the support options that
I’ll be able to drive (acceleration etc), but things seem happy.

One question, is it important to have an ‘input group’ or can I just
use the result of PhInputGroup(NULL) which is the ‘default input group’?

But since this is rather low-level stuff, I don’t think it’s a good idea
for your first Photon project…

Well, since it will probably be my only photon project it will have to
do :slight_smile: (I’m definitely on the low-level side of our project).

\p

Most people want security in this world, not liberty. — H.L. Mencken

d p chang <dpc@wintermute.redjade.com> wrote:

Wojtek Lerch <> wojtek@qnx.com> > writes:

It might be worth mentioning that the SDK is not really necessary to
build an input driver – it just makes typical things easier. A
Photon input driver is just an application that emits Photon input
events (and typically doesn’t display anything).

This is what I was looking for

In the meantime, read the programmers guide-> events section of the Photon
manual.

If you want to write an input driver without waiting for the SDK, look
at the the several paragraphs that explains how to set up the region to
emit raw events from (the third bullet in the “Emitting key events”
section). It is rather vague and you’ll need to search header files for
details, but at least it will point you in the right direction.

I found this and something on the support page for emitting raw
events. I’m still playing around w/ all of the support options that
I’ll be able to drive (acceleration etc), but things seem happy.

One question, is it important to have an ‘input group’ or can I just
use the result of PhInputGroup(NULL) which is the ‘default input group’?

Typically, a driver has a command-line option the tells it which input
group to emit its events from. If that option is not given to your
driver, using the result from PhInputGroup(NULL) is a good choice – it
will let you override the default (1) by setting the PHIG environment
variable.


Wojtek Lerch (wojtek@qnx.com) QNX Software Systems Ltd.