On 28.05.2008, at 11:30, George Petrov wrote: > Some details. In fact this keyboard is not supposed to be used by > other applications (but, hmmm, maybe it's a good idea). KBD is not > needed to be seen even by FLTK (although maybe it's better if it is > possible). I just need to get a notification or maybe I should say: > it is enough if fltk:wait() returns on all events + if something is > pressed on that external KBD. Then I can test whether this is fltk > event or external keyboard is pressed.
If this is purely a serial port keyboard which is not recognize by the system, you can write your own driver. I did that for a serial port 6DOF mouse and that works well. You can use the RS232 code from the DyneTK (http://code.google.com/p/dynee5 ). The SVN contains a class Flio_Serial_Port IIRC which does all the serial communication for you. The class implements a widget which will call its callback whenever serail port data is available. You don't have to implement any multithreading or serial port programming code. Matthias > ---- http://robowerk.com/ _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
