[827] in java-interest
Re: Mouse Buttons
daemon@ATHENA.MIT.EDU (jim frost)
Fri Jul 21 14:17:23 1995
To: krom@cgi.com (Kevin Krom)
Cc: hotjava-interest@java.sun.com, java-interest@java.sun.com
In-Reply-To: Your message of "Fri, 21 Jul 1995 09:26:55 EDT."
<9507211326.AA17286@sawyer.trac2es.com>
Date: Fri, 21 Jul 1995 12:40:23 -0400
From: jim frost <jimf@world.std.com>
|
|> > What about the portability argument - some boxes (e.g. the Mac)
|> > have single buttton mice. You could end up with a problem if
|> > you programmed different actions on buttons 1, 2 (std
|> > DOS/Windows), 3 (std UNIX), 4 or 5 (esoteric X).
|> >
|>
|> so? Thats the problem of mac users. They just dont get the extra
|> functionality.
|
|Don't limit your thinking to the physical device -- instead of looking
|at "right mouse click", "left mose click", et. al., think more in terms
|of "click event 1", "click event 2", etc.
Right.
What I have done in my graphics libraries (which absolutely had to be
portable) was define logical button types -- in particular "select
button" and "option button." Typically the option button is used for
popups; the select button is self-explanatory.
On the PC select is button one and option button two. On UNIX systems
they are one and three. On the Mac it's mouse and mouse+option.
Extra "buttons" can be defined with other purposes, of course.
The beauty of this is not so much that it increases portability, but
that it aids in application consistency. Everybody ends up using the
same events for the same things.
jim frost
jimf@world.std.com
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
