pete at mollysrevenge.com
Tue May 10 14:58:50 EDT 2011
I think that menuHistory behavior is what you'd want most of the time but
just good to make people aware of it, just in case. And yes, selecting the
current selection does trigger a menuPick so that's the way to do get around
the menuHistory behavior if it matters. But then, as you pointed out, you
need to do your own checking for the same selection if it matters...
Molly's Revenge <http://www.mollysrevenge.com>
On Tue, May 10, 2011 at 11:32 AM, Bob Sneidar <bobs at twft.com> wrote:
> Oh hey didn't know that. It is true however, that selecting the current
> menu selection DOES trigger a menupick, which is probably why I thought
> setting the menuhistory to what it already is did the same thing.
> On May 10, 2011, at 11:15 AM, Pete wrote:
> > I think it's also worth commenting on setting the menuHistory to solve
> > 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
> > problem but good to be aware of.
> > Pete
> > Molly's Revenge <http://www.mollysrevenge.com>
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode