Regarding the "looking into the future" i was thinking that we will go the Smalltalk way, by reifying such new events. Instead of "reusing" plain old three button mouse events. And leave the MouseEvent for what they were originally conceived (the proposed renaming )
In this scenario a touch pad would generate a TouchPadEvent, and a multibutton mouse would generate "MultiButtonMouseEvent" Fernando On Tue, Jan 25, 2011 at 10:58 AM, Geert Claes <[email protected]> wrote: > > > Lukas Renggli wrote: >> >> ... >> AFAIK, most operating systems number the mouse buttons. >> >> - The primary button is what you use to perform actions (typically left >> mouse button). >> - The secondary buttons is what you use to open context menu (typically >> right mouse button). >> - The third button is the middle button, the fourth button, ... >> >> Now I see that numbers are not that far from colors, but at least they >> have a logical order. I don't like #select, #menu, #extra because I does >> not make sense in any other context (for example games, or touch >> applications) than a traditional GUI. >> > > Agree, on one side there are the physical buttons (button 1, 2, 3 etc) and > on the other hand there are the events they trigger. e.g. for right-handed > people button 1 would be the primary button where for left-handed this could > very well be button 3. > > Then again, maybe it is time to look a bit further as it looks like the near > future is heading towards a world without any physical buttons where there > is no need to number or name buttons at all :) > > http://www.geek.com/articles/gadgets/new-apple-patent-puts-a-display-on-the-magic-mouse-20110124/ > > Additional gesture events: > http://www.youtube.com/watch?v=JKlkte1aOOw > > -- > View this message in context: > http://forum.world.st/What-about-a-little-rename-in-MouseEvent-tp3233363p3235798.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >
