[FIX] FasterMouseOver-nk ( [closed] )

[marcus at ira.uka.de]

This cs has some problems, as Andreas mentioned (see below). I close
this thread now. An improved version of the cs can be re-submitted
with a different subject.

Here's Andreas post:

Must have missed this post earlier on but I want to point out that this
change will have side-effects. The current mechanism has been made so
that
even if morphs move they will be notified about mouse entry/leave
events.
E.g., if you have a little eToy that does something like:

foo>>script1 [on: mousEnter]
    foo's color <- Color red.

foo>>script2 [on: mouseLeave]
    foo's color <- Color green.

foo>>script3 [ticking]
    foo forward: 5.
    foo turn: 5.

then, upon having foo move under the cursor, the system will correctly
invoke the event responses. With the changes proposed it no longer will.
I
can't say for sure what other implications this has but it's certainly
an
annoyance for eToys - in particular considering that #isUnderMouse will
report true but no events are being generated.