I agree that device messages should all be in one place. There are messages to and from the user, as well as to and from the device.
Hope I wasn't dancing on anyone's toes
So, if all of this will be an XINPUT expansion, this discussion would be better off in the little-used XINPUT list.
There is such a list? Where?
As for control type names, Atoms make a lot of sense, because they readily expandable, unlike integer enumerators as used in HID. It also seems to me that the current Atom managing code would be a reasonable place to create some sort of registry.
Atoms, enumerations, outright strings... I'm not too concerned either way, I only advise taking the opportunity to standardize the vocabulary behind the control name fields, lest we get caught in a mire. We're sort of there already, insofar as clients trying to infer too much meaning from existing XINPUT callback structs will get punished.
Just because I like to incite riots, if it turns out we send XML messages back and forth, I won't be too hot & bothered about it. (Now, duck!)
-- ____ .:. ____ Bryan W. Headley - [EMAIL PROTECTED]
_______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
