Peter Haworth wrote:
> I can separate the row specific items from the others with a line
> but how does that gel with HIG?
IIRC all the HIGs (OS X, Win, Gnome) recommend using separators where
appropriate in pulldown and popup menus, and the LC engine supports them
well on all three platforms
I guess on the theory that no news is good news then any news must be bad!
Back to the drawing board I guess.
I'm thinking I have a couple of choices.
I could use an option menu showing what would have been the main menu items in
the cascading scenario, and either a second option menu that d
Peter Haworth wrote:
The recent thread on mouseDoubleup and particularly Richard's thought
on HIG have made me realise the UI choices I made weren't the best.
I'm now thinking of using a cascading option menu.
The menuPick dictionary entry says "If the menu item is part of
a submenu, the menu i
Thanks, I think I still have problems though.
If the submenu items were constant values, the menuhistory would work, but the
menu choices will be built dynamically when the user clicks on the option menu
button so the menuhistory won't be fixed for any particular submenu item.
The menu tagging
Pete:
There should be no issue here.
In a cascade menu put:
AA : BB
CC
DD
EE : BB
CC
DD
FF
You will want to get the menuHistory in order to distinguish between the
redundant choices:
on menuPick pItemName
put pItemname && the menuhistory of me
end menuPick
I g
