[143] in java-interest
Re: Three things Applets can't do w/ the current API (with proposed fixes)
daemon@ATHENA.MIT.EDU (Scott Hudson)
Mon May 29 19:55:39 1995
From: hudson@cc.gatech.edu (Scott Hudson)
Date: Mon, 29 May 1995 19:39:36 -0400 (EDT)
To: java-interest@java.Eng.Sun.COM
> From Dan.Oscarsson@malmo.trab.se Mon May 29 02:40:48 1995
> To: java-interest@java.Sun.COM, hudson@cc.gatech.edu
> Subject: Re: Three things Applets can't do w/ the current API (with proposed fixes)
>
> An other way is to do what I did in an expremental graphics library. For
> each mouse event apart for position and modifiers, a state was included
> that indicated the number of clicks pressed. This allowed the click handling
> to be handled in the core routines and probably more efficiently.
> Also removed the need for every applet to check against time stamps.
>
I'm not sure I fully understand the approach you are indicating. Are
you saying that the "core" takes the time into account and produces
special double-click (or N-click) events (that is also how I've done
it in the past, and would like to do it in the future), or that there
is some way to do this without taking time into account?
It seems like the "right" definition of double click limits both the time,
and area within which the clicks occur, so there must be an indication
of time somewhere in order to do this right.
Note also that there are other (more obscure, but occasionally useful)
interaction techniques that need an accounting of time. A final reason
I'm interested in having the time is that I am writing a toolkit on top
of AWT and would like to do the click/double-click processing myself
(but can't).
Scott Hudson
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
