LiveCode Forums.

Hi,

This looks like the right way to go, but as it stands, the "menupick" seem not to be able to choose the right picking (it does return a choice form the menu, but usually not the right one)

Hi Daniel,

well that is a hack, but a clever one

And is, as I said, probably NOT what most useres are exspecting!
At least I would be heavily surprised by that

Better stick with standards!


Best

Klaus

I understand what you say, Klaus, and this is probably the right frame of mind for most occasions, but in other cases I think it depends on context.
Say you've made an app to classify every object crossing the road on wheels (you're a cop with too much free time). You choose from a cascade menu like this one (Don't worry about the rationality of the rationality of the classification approach, I just made up the example; in real life you'd probably use another way to classify things)

Car
Berlina
Ford
Mondego
Diessel
...
...
Mercedes
Honda
SUV
Toyota
...
Bicicle
Mountain Bike
Titanium chasis bike
Race BIke
Motorcicle
Trial
Motocross
...
Truck
...

Did I mentioned you had too much idle time?
Well the point is that you want to be as specific as you can but you can't hope to cover all the possibilities, so that the subchoices, at least in some cases, does not exhaust all the possibilities. When the user understand that point I don't think he or she will find a bug if the app accepts as a valid selection a picking that is below the last degree of specificity. Well, that was the idea at least. I'll have another look at mwieder's clever hack and see if I can fix it!

Hi Daniel,

yep, I understand that there might be some non-standard requirements!

(you're a cop with too much free time)

Oh well, I SURE know what you mean here


Best

Klaus

Also keep in mind you can add a menu entry wherever you need it that does NOT have subchoices, and this will help a) keep the format as expected for UI standards. (overriding standards as you say though might work better for your purposes, just mentioning an option here)

So that you have

car
truck
boat
rv
plane

And inside car
Current Level
chevy
ford
lincoln

If they choose current level it will return Car|Current Level (or whatever you want to call your special entry) check for Current level in your menupick and act accordingly. The downside of course is that you could greatly expand the number of entries in your menu depending on what you actually need to do. The other method is a really snazzy way to avoid that issue.

danielrr wrote:Say you've made an app to classify every object crossing the road on wheels (you're a cop with too much free time). You choose from a cascade menu...

Ouch. Makes my hand hurt just thinking about trying to mouse through so many long and deeply nested menus.

Klaus was merely being helpful. Even the Apple HIG notes that hierarchical menus are physically difficult to use.

With so much data to navigate, have you considered Miller columns instead? Simpler to code, and much simpler to use for large hierarchies.

With so much data to navigate, have you considered Miller columns instead? Simpler to code, and much simpler to use for large hierarchies.

As much as I personally dislike nested menus, if it were me ^^^^^^ sounds like a great solution.

"Simpler to code"? Do you have sample code (especially as a generic form)?
I like the idea, but I haven't tried to implement Miller columns.

I suppose I should qualify "eaiser to build": they're easier if you're handling a knonw number of levels. Working with single-object trees like hierarchical menus require that you're able to build everything out at once, but with Miller columns you only need to build the next level when an item in the previous level is selected. Really good for file systems (why they've been popular in NeXT and OS X), and other large collections.