On 14/01/2010 12:51, Dave Cragg wrote:
On 14 Jan 2010, at 10:13, Richmond Mathewson wrote:
All USB devices will send some sort of keyDown signals and/or pointer movements
to the system; as long as you can interpret those keyDowns inside your stack
there is
no earthly reason why your USB device won't work with RunRev.
I don't think that's right. Each USB device identifies what "class" of device
it is, and the host device (computer) loads the appropriate driver. One such class is
Human Interface Device which covers keyboards, mice, etc. If the device is of that class,
then you should be able to get key messages. But there are other classes (Audio,
Communications, Vendor Specific, etc.) where key messages probably aren't sent.
http://en.wikipedia.org/wiki/Universal_Serial_Bus#Device_classes
Yes, you are right; I'm sorry, I was thinking only of the class of USB
devices such as:
Mice,
Keyboards,
Gamepads.
Dancepads,
Trackballs,
Joysticks,
Steering wheels,
Foot pedals,
and so on (data entry USB devices - I suppose).
The situation ca be complicated; for instance
my Belkin Nostromo n52 (now obsolete, but c.f.
http://catalog.belkin.com/IWCatProductPage.process?Product_Id=390404 )
requires settings to be set outwith the target program before it can
interact with that program.
I had to set up a settings file called "Revolution" using the Nostromo
Preference Pane (Mac OS X) so that
when I pressed button 06 it would paste from the clipboard.
If you are 'just' developing your stack for your own use then you should
have no problems, but, in the
case of authoring for other end users who may have USB devices with
user-editable settings you will
be up a gum tree.
Apart from my 'blah' above; the thing to know is whether your target USB
device has USER-EDITABLE settings.
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution