Florent THIERY wrote: > Sounds like a good idea to me ! > > Add to this the possibility to use the IR transceiver as if it was > really on the host computer... > > But then there would be no need for the daemon anymore.... > Using the joypad API won't help that much I think. We have many inputs, not just 4: - wings & head - light level - IR codes - future: battery level Some of those inputs are on events, some are on polling (which could be also on events if there is a trigger level in the firmware such as low batt warning)
We have many outputs, more than what feedback joystick API could offer - eyes, mouth, wings, spin movements - eyes leds, IR led We have still the major issue to be dealt by a daemon: allowing multiple applications to interact with the Tux. And having a "false" joystick being the Tux could make strange thinks with games using automatically any found joystick... Phil ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ tux-droid-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tux-droid-user
