firing mouseEnter msg of an Image control which was painted
iowahengst at mac.com
Mon Feb 2 13:11:56 EST 2015
How about something like this in the card script?
if the mouseLoc is within the rect of image "imageDemo" then
put "mouseLoc entered"
put "mouseLoc not in image"
> On Feb 2, 2015, at 11:41 AM, Bernard Devlin <bdrunrev at gmail.com <mailto:bdrunrev at gmail.com>> wrote:
> Craig, it is even stranger than that :)
> If you use the eraser to remove all paint, then as you say, such messages
> (e.g. mouseWithin) are not fired.
> If you set the imageData to empty, such messages (e.g. mouseWithin) are not
> If you set the text of the image control to empty, such messages (e.g.
> mouseWithin) do fire.
> On Mon, Feb 2, 2015 at 5:11 PM, <dunbarx at aol.com <mailto:dunbarx at aol.com>> wrote:
>> 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
>> 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.
> use-livecode mailing list
> use-livecode at lists.runrev.com <mailto: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 <http://lists.runrev.com/mailman/listinfo/use-livecode>
More information about the use-livecode