But given you can use the mouse in metro, does it then reverse the situation and take you back to the desktop if you click rather than double tap, this Is really only an issue on a desktop or laptop with a touchscreen, or anything opened in metro is opened in metro to keep it simple, the desktop is only where the exception exists.
I wonder if on the back of these thoughts then if there is some merit that during setup you can choose whether you have touch screen etc, a simple couple questions that invoke a default template that sets the file associations in line with your input method and predicted usage, its never going to be perfect though.
I'm strictly talking about opening files from the desktop/File Explorer. If you're already in metro, you would stay in metro. In fact, in metro there aren't that many opportunities to fall foul of default programs because you have limited exposure to the file system. The vast majority of the time you are already in the app you want to use. It's an app-first rather than file-first workflow.
So yes, an example would be a picture file and a video file on the desktop. If you double click the picture and/or video file it would open up in the normal desktop previewer and/or Windows Media Player respectively. If you double tapped the picture/video it would open up in the touch-centric picture app/Xbox video instead. This would stop desktop and non-touch users getting p***ed off at files getting opened in full-screen apps.
Case in point: Internet Explorer. Windows 8 gets a lot of stick for having two versions of IE, but it's a necessary evil. If you click a link in a Word document it will open in the metro style IE. That's almost certainly not what you want. Now imagine if you CLICK the link it opens in desktop IE, and if you TAP the link it opens in the metro style IE. Wouldn't having two versions then make a lot more sense?
Intelligent default programs based on the way you open files would also cut down a lot of the 'jumping' in and out of metro, another big complaint of desktop users.
Bear in mind that this is NOT the same as 'disabling' or avoiding metro. If the user is opening a file from the desktop AND using a mouse/keyboard command to do so, then it is obvious that they have chosen a desktop-oriented approach and that should be reflected in defaulting to the appropriate app(lication). If you open a file from the desktop with a touch gesture, then you are obviously comfortable with the input method and it's implicit that you wish to work on the data in this way. Of course, these are just default suggestions and could be changed easily just as you normally would.
Is this detracting from/discouraging use of metro style apps 'on' the desktop i.e. snap view? No, not at all. If you see value in a metro app, you will use it. And yes you can use metro style apps perfectly well with a keyboard and mouse, but remember we're only talking about default programs from the desktop.
The problem with a setup-based install option (aside from the fact it would have to be a per-user selection and not a system wide default) is - what would you select for a hybrid device? You wouldn't necessarily want or be able to choose up front which you prefer. My suggestion would be consistent, require no set-up, scale across all form factors and scenarios and be easy to teach. It would become just a normal convention. Click for WIMP, touch for touch.
