I do ask however, why did you make a LCDproc client, instead of writing a direct driver to your LCD display and make a subclass of the LCD stufff?
It's a start, I think it can be usefull while waiting for real specific LCDs drivers but i agree with u, it's not really plug and play.
+ I only have one LCD display and it's integrated on my case in my "production" environment, so i can't really test using it.
What LCD/VFD display do you use?
I'm using a Soundgraph iMON IR/VFD, I'll try to make a specific driver but I can't guarantee
thanks for the advices about the Wiimote, but actually I did go in another direction...
I'm using wiiuse library (http://www.wiiuse.net/
) so I can connect any Wiimote in the range pressing 1+2 button.
I've created a IR-Remote-type device template and each Wiimote key pressed will send command just like remotes do("left", "right" etc...).
I can configure the key mapping using the device data.
The accelerometer could send mouse-move command to the orbiter(not implemented yet).
It works great for the moment and I do not have inquiry error.
I'll post the sources soon.