Hi Mark, Thanks for the update. I guess it depends on the definition of a bug but to be honest, I think the way this works currently is what I'd expect - no menuPick because nothing new got picked. If processing is needed even though nothing changed, you can send a menuPick message, that way there's flexibility.
Of course, I'm definitely biased because I'm relying on the current behavior of menuHistory in some of my code. Pete Molly's Revenge <http://www.mollysrevenge.com> On Wed, May 11, 2011 at 2:49 PM, Mark Wieder <mwie...@ahsoftware.net> wrote: > Pete- > > Wednesday, May 11, 2011, 9:44:31 AM, you wrote: > > > That's strange because that's not what I'm seeing - no wonder there's > > confusion! Here's what I did to test. > > > Put an option menu on a card with the default choices. > > I just reopened bug #9301. It's fixed for pulldown and popup menu > buttons, but not for option menus. > > -- > -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
