[149] in java-interest
Re: Three things Applets can't do w/ the current API (with proposed fixes)
daemon@ATHENA.MIT.EDU (Dan.Oscarsson@malmo.trab.se)
Tue May 30 12:12:11 1995
From: Dan.Oscarsson@malmo.trab.se
Date: Tue, 30 May 95 08:26:04 +0200
To: java-interest@java.Eng.Sun.COM
>>
>> 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.
Yes, I meant that the "core" uses the time, and of course the place, to
identify events that are clicks. And even if it is done this way,
each mouse event could include both information of "click"-state and time
allowing most applications to use use the click-state, and other use the
time information for more complex things.
Dan
--
Dan Oscarsson
Telia Research AB Email: Dan.Oscarsson@malmo.trab.se
Box 85
201 20 Malmo, Sweden
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
