Andreas Beck wrote:
> /* Deviceinfo stuff
> */
> int giiQueryDeviceInfo (gii_input_t inp, uint32 origin,
> gii_cmddata_getdevinfo *info);
> int giiQueryDeviceInfoByNumber(gii_input_t inp, uint32 number,
> uint32 *origin, gii_cmddata_getdevinfo *info);
> int giiQueryValInfo (gii_input_t inp, uint32 origin,
> uint32 valnumber, gii_cmddata_getvalinfo *info);
nice. But how do I know all available origins ?
Hmm, could it be that the 'number' is a simple index (from 0 upwards) which
I use to get device indo as well as the origin ? How do I know at what number
to stop ?
Sorry for these very basic questions. But I didn't find a single mention of these
methods in the docs. *sigh*
> However please note, that you should be prepared to have devices dynamically
> popping up or disappearing.
yeah, right.
> So when the app gets an event from an unknown source, it should not freak
> out, but rather dynamically update its tables.
>
> > is a little event mapping framework such that I can map between event
> > types such that I can use my stylus as a generic mouse replacement (i.e.
> > map from valuators to positions), etc.
>
> That is what filters (for common special cases) or LibGIC (universal
> including an interactive configuration mechanism) are for.
ok, as I illustrated in another reply, I don't think I can do that since our
event type system is pretty different from the one in GII/GGI. However, once
I have established a working mechanism, I'll happily use as much of GII and
extensions as I can to implement it.
Regards,
Stefan
