object beneath mouseLoc?

[Richmond Mathewson]

On 07/04/2011 09:51 PM, Ken Ray wrote:
>>> Personally I'd like to kick that concept to the curb and have all mouseXXX
>>> function relate to where the actual mouse *is*, regardless of whether it's
>>> state is up or down...
>> That would break scripts that need to act on mouseRelease, wouldn't it?
> OK, you're right about mouseRelease; that should still be be sent to the
> original object, but I'd still do it for mouseEnter, mouseLeave, mouseMove,
> mouseWIthin, mouseChar, mouseCharChunk, mouseLine, mouseControl, mouseColor,
> and mouseText...
>

It threw me somewhat, when I realised that mouseLeave was dependent on 
the mouse button being up; a bit counter-intuitive.
> :D
>
> Ken Ray
> Sons of Thunder Software, Inc.
> Email: kray at sonsothunder.com
> Web Site: http://www.sonsothunder.com/
>
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode