Ok. I definitely think that a return value would make driver message more useful. I'll try to implement this soon, and change the naming convention for drivers somehow.
Quoting Pascal Bauermeister <[EMAIL PROTECTED]>: > Micah Dowty wrote: > > > > Actually, it should be possible to create an "input" driver that > doesn't do > > anything except respond to driver messages. I've actually been > thinking about > > renaming input drivers to 'generic' drivers, so we have video drivers > and > > generic drivers. There could only be one video driver at a time, and > it would be > > special-purpose, but there could be any number of generic drivers to > handle > > input, power management, sound, etc. > > Good. This will be cleaner. For now we'll use an input driver to treat > driver msgs. > > Another question: sometimes we would like to ask the driver a question > (like: is > your hardware connected ?). Is there anything foreseen for this purpose > ? (A > possibility could be to have drivermessage() and pgDriverMessage() > return a long). > > > > > Quoting Pascal Bauermeister <[EMAIL PROTECTED]>: > > > > > Hello Micah, > > > > > > The driver messages are a great thing to handle extraneous events. > As I > > > understand, they are sent to the active video and input drivers. > > > > > > I would like to bind an extra driver specifically dedicated to > handle > > > several kinds of messages. How is it possible ? > > > > > > Regards, > > > > > > Pascal > > -- > Pascal Bauermeister > Head of Software Development > > SMARTDATA > PSE-A / EPFL > CH-1015 Lausanne > > http://www.smartdata.ch > mailto:[EMAIL PROTECTED] > Phone: +41 (21) 693 84 98 > fax: +41 (21) 693 84 91 > > _______________________________________________ > Pgui-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/pgui-devel > -- Only you can prevent creeping featurism! _______________________________________________ Pgui-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/pgui-devel
