by Bret » Wed Nov 28, 2012 9:09 am
Well, I don't have a touch screen myself, but always figured if I did I would probably have it work pretty much like a mouse and actually let a mouse driver (CTMOUSE) communicate with the application. My program would just feed the movement and button information to the mouse driver, similar to how USBMOUSE works now. Having never seen how a touch screen interface actually works, though, that may be a bad idea. Plus, the application itself would need to understand what to do with the mouse input. It might be better to have it simulate a keyboard pressing arrow keys and then the enter key.
USBKEYB is similar to USBMOUSE, but does have two-way communications built into it (it issues commands to turn the keyboard LEDs for Cap/Num/Scroll Lock on and off). I don't know if that is similar to what the touch-screen controller requires for communications or not. I can send you both USBMOUSE and USBKEYB if you want, but I'll do it privately since they aren't ready for official release just yet.