Well, you can now officially disable it in settings instead of using a registry hack.
Loading user information from Channel 9
Something went wrong getting user information from Channel 9
Loading user information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Or you could just use their numpad layout minus the crammed in arrow keys and map the down arrow to 5 when in arrow mode instead of (or in addition to) 2 instead of shifting almost every fricken key between modes.
PS: Those editing/navigation keys have standard positions on the numpad too. And they've been there even longer than the AT-style keyboard.
What doth y'all think? I think it looks sweet. It's the kind of thing they should have done from the start (pun intended) IMHO.
PS: And Modern apps running in windows!
@DCMonkey: It seems that the post is indicating that it is better not to have the warnings than to have potentially poor implementations of the warnings, which might lead folks to think their code is fine when it isn't.
Great... I'm down with this, it makes sense.
Except one part: the compiler still accepts the switch! So now you think you have at least a mostly-working implementation of the warnings, but in reality there are no warnings!
Well, the post stated they would eventually remove the option, but I don't know if they ever did. In any case, I forgot that Apple uses the clang compiler front end these days so I don't think that post applies in this case after all.
Thanks for the explanation. That makes sense. In many contexts that would be advantageous. In regards to charms people have used infinite edge to justify how great the feature is and easy for users to access because of it (and by no means am I suggesting you are one of those people or that you even like the charms implementation). What they overlook is the mouse actions after the target has been hit and how easy it is to slide off the charms bar while moving up or down the bar which causes the bar to disappear. So again in the right context infinite edge makes sense.
I find the right corner then down the side gesture for the charms bar awkward, yet the left corner and down for the metro window list isn't too bad. I'm guessing left-handers would find the opposite is true. It could also be that I use a thumb trackball and moving down and to the left is easier that down and to the right
Actually, the pixel under your current mouse position (ie: for context menus) is the most valuable.
And personally, I would ditch the charms bar activation by mouse and give the top right corner to some subtle window controls that fade in as you approach them.