It is still a curious question. Should widgets be aware of the message lock state (and not post) or is it a bug or is there another explanation? On Tue, May 8, 2018 at 6:36 PM Ralph DiMola via use-livecode < use-livecode@lists.runrev.com> wrote:
> That's what I finally did. App works now. Thanks! > > Ralph DiMola > IT Director > Evergreen Information Services > rdim...@evergreeninfo.net > > > -----Original Message----- > From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On > Behalf > Of dunbarx via use-livecode > Sent: Tuesday, May 08, 2018 5:01 PM > To: use-revolut...@lists.runrev.com > Cc: dunbarx > Subject: Re: Navigation Widget Suppressing the hiliteChanged Message > > Instead of locking messages, can you not include a hilitedChanged handler > that will trap and bury the message? Not sure where the best place for that > would be. > > Craig > > > > -- > Sent from: > http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html > > _______________________________________________ > 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 > _______________________________________________ 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
