What's On The Menu?

[Peter Haworth]

I'll use LC as an example.  Lets say you have an application that needs to
provide the ability to pick a card from any of the open stacks.  The option
menu would list the stacks with subitems for the cards in each stack.

Same sort of thing for perhaps CDs in a music collection.  The first level
items are the CD names and the second level would be the tracks on the CD.
 You could even imagine a three level hierarchy in that instance - Artists,
CDs, tracks.

I'm happy to use a pulldown menu but its behavior just seems odd in terms
of the menuHistory not being reflected in what's displayed in the menu.

Pete
lcSQL Software <http://www.lcsql.com>


On Sat, Dec 29, 2012 at 3:17 PM, Mark Wieder <mwieder at ahsoftware.net> wrote:

> Pete-
>
> Saturday, December 29, 2012, 2:13:06 PM, you wrote:
>
> > It seems that you cannot have cascading items in an option menu.  The
> > secondary items appear as first level items with a tab before them.
>
> > As far I can tell, I have to use a pulldown menu to be able to use
> > cascading menu items.  However, no matter which item you choose on a
> > pulldown menu, when the choice has been processed, the pulldown menu
> shows
> > its first item not the one that was selected.  The menuHistory of the
> > pulldown menu is correct but I have to set its label to get the chosen
> item
> > to show.
>
> > So, no cascading items on option menus and menuHistory has no effect on
> > pulldown menus.  Is that all expected behavior?
>
> I'm not sure I've ever seen (or wanted) a cascading option menu on any
> application. Is there an advantage to using an option menu for this?
> Can you point me to any application that's got one?
>
> --
> -Mark Wieder
>  mwieder at ahsoftware.net
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>