Thanks Sven!
BTW, as an enhancement for 2.2.2.0, you could treat unnamed mouse buttons.
Mouses with more axis and more buttons are becoming increasingly common, and
"unmarshalMouseButton" is not prepared to accept them!!
Here are exceptions I caught, playing with my Genius Traveler 515 mouse:
unmarshalMouseButton: illegal value 5
unmarshalMouseButton: illegal value 6
unmarshalMouseButton: illegal value 7
unmarshalMouseButton: illegal value 8
Anyway, keep the good work!
Best Regards,
Rafael
On Sun, Aug 16, 2009 at 13:12, Sven Panne
A new version of the GLUT package has been uploaded to Hackage.
* The package is now autoconf-free. API entries are resolved dynamically at runtime, just like the OpenGLRaw and GLURaw packages.
* Support for sRGB framebuffers has been added, just use SRGBMode with initialDisplayMode. To use this functionality, you need the upcoming freeglut 2.6.0 library, older versions and "classic" GLUT do not support this feature.
* Support for context profiles has been added via initialContextProfile. Again, this works with the upcoming freeglut 2.6.0 library only.
Cheers, S. _______________________________________________ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
-- Rafael Gustavo da Cunha Pereira Pinto
Am Sonntag, 16. August 2009 22:10:23 schrieb Rafael Gustavo da Cunha Pereira Pinto:
BTW, as an enhancement for 2.2.2.0, you could treat unnamed mouse buttons. Mouses with more axis and more buttons are becoming increasingly common, and "unmarshalMouseButton" is not prepared to accept them!!
Here are exceptions I caught, playing with my Genius Traveler 515 mouse:
unmarshalMouseButton: illegal value 5 unmarshalMouseButton: illegal value 6 unmarshalMouseButton: illegal value 7 unmarshalMouseButton: illegal value 8
Good point, I had similar reports already, but I simply forgot to handle this in yesterday's release. The right way to handle this would probably be extending the MouseButton data type with an 'AdditionalButton Int' constructor and simply pass the unknown button numbers via this case. I am not so sure about a nice name for this constructor: AdditionalButton? GenericButton? Or simply MouseButton, just like the type itself? Cheers, S.
On Mon, Aug 17, 2009 at 03:17, Sven Panne
Am Sonntag, 16. August 2009 22:10:23 schrieb Rafael Gustavo da Cunha Pereira Pinto:
BTW, as an enhancement for 2.2.2.0, you could treat unnamed mouse buttons. Mouses with more axis and more buttons are becoming increasingly common, and "unmarshalMouseButton" is not prepared to accept them!!
Here are exceptions I caught, playing with my Genius Traveler 515 mouse:
unmarshalMouseButton: illegal value 5 unmarshalMouseButton: illegal value 6 unmarshalMouseButton: illegal value 7 unmarshalMouseButton: illegal value 8
Good point, I had similar reports already, but I simply forgot to handle this in yesterday's release. The right way to handle this would probably be extending the MouseButton data type with an 'AdditionalButton Int' constructor and simply pass the unknown button numbers via this case. I am not so sure about a nice name for this constructor: AdditionalButton? GenericButton? Or simply MouseButton, just like the type itself?
Cheers, S.
AdditionalButton seems good. My second choice would be to use MouseButton. -- Rafael Gustavo da Cunha Pereira Pinto
Sven Panne wrote:
and simply pass the unknown button numbers via this case. I am not so sure about a nice name for this constructor: AdditionalButton? GenericButton? Or simply MouseButton, just like the type itself?
How about OtherButton? Martijn.
participants (3)
-
Martijn van Steenbergen -
Rafael Gustavo da Cunha Pereira Pinto -
Sven Panne