Indeed, as I said in the original post, I'd done that whilst testing, (and for display to some newbies), but it is necessary to remove the duplication before writing to the xml file.
Indeed, as I said in the original post, I'd done that whilst testing, (and for display to some newbies), but it is necessary to remove the duplication before writing to the xml file.
True, but think it the other way. If false for mnemonics was the default choice (you have to have a default choice). Then again you would need to search for it. And beginners wouldn't know the term mnemonics which would make searching for it more difficult to achieve the desired operation.
So these kind of decisions from MS part are not easy. That is why they change things with every new release and there are always complains.
My personal preference would be to keep it simple for beginners, thus agreeing with you. And enable options to change default parameters, so advance users wouldn't set Mnemonics always true with each label created. But then you have the marketing question. If you set everything simple by default, the new user might not learn its many features and never use them. Now you are encouraged to look upon the many options available.
So, as expected, I would say that MS has the right policy, not meaning that they do everything right. Even thought I would want a different policy.
The same goes for other API. I was using QT, for example, and I spent a lot of time trying to figure out how to set the background color of a control exactly the way I want. What it did was to inherit it from a parent control. So I disabled that feature. And again didn't work. I had to change an application variable, sth like an enviromental variable, to make it work the way I want. Impossible to find without searching the internet.
Also, remember, this is a legacy feature. For the first versions of Windows, it WAS a very good idea to make everything use mnemonics by default, because the first versions were designed to be fully usable to users without a mouse -- which at the time was rare to see in the personal computing world.
Even today, I'd say for most form elements it's desirable to use mnemonics, because people who will use your program regularly will often find the keyboard to be much faster than the mouse.
You ever try a pink golf ball, Wally? Why, the wind shear on a pink ball alone can take the head clean off a 90 pound midget at 300 yards.
Test to see if its got 7 characters minus the extra &:
Code:if (lblMessage.Text.Replace("&&", "&").Length == 7) { // code if true goes here }