Hmmm, well I just tried it and got no menuPick when I set the menuHistory to its existing value (running 4.6.0.)
I read the text of the bug report and it's a little confusing about what actually got fixed or even if anything did. My reply was strictly to do with option menus but the bug report seems to be referring to pulldown/popup/cascade menus, although even then, I'm not sure what got fixed. So I stand by my original comment about this, at least as far as option menus are concerned. And if indeed it did change and I'm somehow not experiencing the change, then it would be great if the user comment in the dictionary was either updated or deleted. Molly's Revenge <http://www.mollysrevenge.com> On Tue, May 10, 2011 at 5:51 PM, Mark Wieder <mwie...@ahsoftware.net> wrote: > Pete- > > Tuesday, May 10, 2011, 11:15:38 AM, you wrote: > > > I think it's also worth commenting on setting the menuHistory to solve > this > > problem. If a handler sets the menuHistory to it's existing value, no > > menuPick message is generated. I can't tell if that's significant to > this > > problem but good to be aware of. > > That's a bug (#9301) that got fixed in the 4.6.0 release. > > -- > -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
