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 "in
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
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 i
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
--
