No subject

Making a script fire on mouseStillDown, and holding the button fires at some high unknown rate. Perhaps it should be governed by the ticking rate. And by the ticking rate setting also.

In the Lunar Lander, gravity is ticking. Make a button that counteracts it when mouseStillDown. It will run about 10 times as often than the ticking script.


(scott) 

Hmm... this sounds like a pretty good idea.

However, of course, the mouse-still-down is dispatched by the basic morphic event-handler mechanism, not by the ticking mechanism.

But in an ideal world (rather than one in which we take what Morphic will give us,) yes, perhaps we should put the frequency of dispatch to scripts triggered by mouse-still-down under the user's control.

Conceptually, script set to trigger on mouse-still-down could be thought of as an always-ticking-script guarded by whether the mouse went down in the object and is still down. But implementation, transcending the worlds of event-dispatch and ticking, might be tricky. Probably not a priority anytime soon.



    Fix Version: someday
                     (was: triage)

Given the trickiness involved, and the fact that this is more a strangeness than a true bug, I think this is best deferred into the "someday" bin for now.

> mouseStillDown -- rate of dispatch
> ----------------------------------
>
>          Key: SQ-121
>          URL: http://tracker.immuexa.com/browse/SQ-121
>      Project: squeakland
>         Type: Improvement
>   Components: etoys
>     Reporter: team
>     Priority: Eventual
>      Fix For: someday

>
>
> From TRAC ticket 7611 (ted kaehler, july 2008)
> Making a script fire on mouseStillDown, and holding the button fires at some high unknown rate. Perhaps it should be governed by the ticking rate. And by the ticking rate setting also.
> In the Lunar Lander, gravity is ticking. Make a button that counteracts it when mouseStillDown. It will run about 10 times as often than the ticking script.
> (scott) 
> Hmm... this sounds like a pretty good idea.
> However, of course, the mouse-still-down is dispatched by the basic morphic event-handler mechanism, not by the ticking mechanism.
> But in an ideal world (rather than one in which we take what Morphic will give us,) yes, perhaps we should put the frequency of dispatch to scripts triggered by mouse-still-down under the user's control.
> Conceptually, a script set to trigger on mouse-still-down could be thought of as an always-ticking-script guarded by whether the mouse went down in the object and is still down. But implementation, transcending the worlds of event-dispatch and ticking, might be tricky. Probably not a priority anytime soon.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://tracker.immuexa.com/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira