Sure, I understand I can check things in menuPick. I guess it comes down to what's the behavior that works most of the time for most people, making that the default, and providing a way to get round the default if it's not what you want. In this very personal sample of one (me), I have yet to come across a situation where I want menupick in an option menu to be triggered if I set the menuhistory to its current value, so it's kind of a pain to have put a workaround for that in every menuPick handler I code.
But, you definitely have seniority over me, so I respect your opinion ;-) And I'll just enjoy the way it works now until ti gets changed and then change all mu code to deal with it. Pete Molly's Revenge <http://www.mollysrevenge.com> On Wed, May 11, 2011 at 6:39 PM, Mark Wieder <mwie...@ahsoftware.net> wrote: > Pete- > > Wednesday, May 11, 2011, 3:26:28 PM, you wrote: > > > Of course, I'm definitely biased because I'm relying on the current > behavior > > of menuHistory in some of my code. > > <g> OTOH, it's easy to check for the current value in the menuPick > handler and exit if it's the same. > > The reason for bug #9301 in the first place was that selecting > menuitems from a menubar from a scripted solution wouldn't always > work. So on the way to fixing menus, popup and pulldown menus got > fixed. Option menus are "broken" because they now don't act the same > as other menu buttons. > > That's my story and I'm sticking to it. > > -- > -Mark Wieder > mwie...@ahsoftware.net > > > _______________________________________________ > 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
