This is too much. It is a bug. Though an interesting feature might be the addition of new messages, something like "paintEnter" or "paintWithin". But these should always be either nonexistent, or separate from the enclosing image.
Anyway, I posted earlier that even if you erase all the paint that you once placed inside, the message lockout persists in the image. This to me is a source of wonder and irritation. It should not be permitted that an "overlay" of paint changes the properties of the object over which it lies. No other object sandwich works that way, or ought to. Craig -----Original Message----- From: Bernard Devlin <bdrun...@gmail.com> To: How to use LiveCode <use-livecode@lists.runrev.com> Sent: Mon, Feb 2, 2015 10:55 am Subject: Re: firing mouseEnter msg of an Image control which was painted Putting a mouseWithin handler within the image shows that this message too is not fired, unless the mouse pointer is over a painted area. Again, once the image is selected, then mouseWithin is sent even when the pointer is over a non-painted area. Bernard On Mon, Feb 2, 2015 at 3:10 PM, Bernard Devlin <bdrun...@gmail.com> wrote: > And another oddity: > > once a painted image control is selected, then mouseEnter is fired upon > entering the rect of the control. > > Bernard > > > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
