On Mon, Aug 17, 2009 at 03:17, Sven Panne <sven.pa...@aedion.de> wrote:
> 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
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
