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.
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 > > > -- > Experience is what causes a person to make new mistakes instead of old > ones. > > _______________________________________________ > 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
