Hi Andreas,

The original post was pretty old (sometime last summer).

I will close the allready approved thread, so this won't
end in the update stream bu accident.

      Marcus

Am 29.02.2004 um 17:26 schrieb Andreas Raab:

> Hi Guys,
>
> 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.
>
> Cheers,
>   - Andreas
>
>
> ----- Original Message -----
> From: <marcus at ira.uka.de>
> To: <squeak-harvest at lists.squeakfoundation.org>
> Sent: Sunday, February 29, 2004 4:46 PM
> Subject: [FIX] FasterMouseOver-nk ( [sm][et][approved] )
>
>
>>
>> No Conflicts. Changeset by Ned,reviewed by Tim and Daniel. Thus:
>> Approved.
>>
>
>
--
Marcus Denker marcus at ira.uka.de