Crash-a-lot just became critical
Mike Bonner
bonnmike at gmail.com
Fri Jan 9 13:09:22 EST 2015
That is definitely different. I won't need to put a background grc or
image (or whatever) to catch the mouseenter anymore, but I can see it
causing weird stuff. What about empty space in groups? Just checked, they
still behave the old way. Enter a group, but not over a control, and no
mouseenter is sent.
On Fri, Jan 9, 2015 at 11:03 AM, J. Landman Gay <jacque at hyperactivesw.com>
wrote:
> On 1/9/2015 8:02 AM, Peter M. Brigham wrote:
>
>> Are people saying that in some newer versions of LC the mouseEnter
>> message is not sent to the control being entered but rather directly
>> to the stack?
>>
>
> No, that part behaves as it always did. Controls receive mouseEnter
> normally. Previous versions of the Mac engine did not send the message to
> the card or stack if there was no control under the mouse though. In LC 7
> it does. Apparently it always did that on Linux, so the behavior was
> specific to the platform.
>
> You can test by creating a new stack without any controls, just a blank
> card. Put a mouseEnter handler into the card or stack script. Move the
> mouse into the stack window. In LC 6.x nothing will happen. In LC 7 the
> handler will execute.
>
> --
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.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
>
More information about the use-livecode
mailing list