It would be better to do something like add another handler to the button: on MouseUpWithHilite set hilite of me to not hilite of me mouseup end MouseUpWithHilite
And send THAT message to the button from afar. This way, the existing MouseUp handler in the button works as expected, and this message has the same result as clicking the button (toggling the hilite in the process) and enacting the MouseUp handler. ~ Chris Innanen ~ Nonsanity On Tue, Feb 15, 2011 at 11:52 AM, Robert Brenstein <r...@robelko.com> wrote: > On 15.02.11 at 17:24 +0100 Tiemo Hollmann TB apparently wrote: > >> Hi Jim, >> thanks for your coaching. I wasn' t aware that sending the mousup message >> wouldn't trigger the needed event. >> So I was correct that I have to script both the message and the event. >> Thank you >> Tiemo >> > > In this case, you can use click instead of send: > > click at the loc of btn "test" > > This will create the event and send the mouseUp. > > Robert > > > _______________________________________________ > 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