Wasn't this feature built into versions of VB previous to VS.NET 05? I seem
to remember the ability to indicate that a particular set of menu options
was mutually exclusive i.e. a dot would appear next to the single item
selected.
I can live with the fact that I now have to code something that used to be
done with setting control properties, but what irks me is that the visual
interface is no longer consistent. Checks are for non-mutually exclusive
options. Dots are for mutually exclusive options. This used to be true
outside and inside a menu. But with the apparent removal of this feature,
the interface standard is no longer uniformly applied.
Using the example below, in VS.NET 05, if I see a check next to Yellow, I
don't automatically know that I'm only allowed to select one option.
Depending on the application, it may not be intuitive that you can't select
any combination of the options.
Yeah, I guess I could always write my own control, but that's not the point.
It seems like MS has abandoned applying one of the most fundamental GUI
principles when it comes to the Menu. Am I the only one bothered by this?
Mitchell S. Honnert
www.UltraID3Lib.com
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:O2**************@tk2msftngp13.phx.gbl...
"I Don't Like Spam" <no@spam.com> schrieb: How do I create a submenu so that I can only check ONE of the values?
Example:
Menu
--> Color SubMenu
--> Red Value 1
--> Yellow Value 2
--> Green Value 3
Thanks....
You have to unclick the other items yourself once on is selected.
You can simplify this by storing the selected option in a private variable
of type 'MenuItem', for example, then uncheck the previously checked item
if another item is clicked and store the newly checked item in the
variable.
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>