Linked by Thom Holwerda on Fri 23rd Apr 2010 23:34 UTC
Hardware, Embedded Systems So, we have Microsoft slowly but surely trying to be a better citizen in the computing world - with the emphasis on trying. After years of dragging their feet, the company is finally implementing web standards in Internet Explorer, there's a boatload of interoperability information now, that sort of stuff. And then, just when you think they're starting to get it - they go behind our backs to do something incredibly insipid. It's small, you'll barely notice it, but dear lord, it's really, really annoying.
Thread beginning with comment 420576
To read all comments associated with this story, please click here.
Not the only way
by PlatformAgnostic on Fri 23rd Apr 2010 23:44 UTC
Member since:

This isn't the only way or even the best way for a PC manufacturer to implement that bullet-pointed recommendation.

I don't see how this is Microsoft's fault. The hardware does not have to generate WIN+P from the keyboard controller to validly invoke the dialog box. It might just be the easiest way to accomplish the goal.

Reply Score: 6

RE: Not the only way
by Thom_Holwerda on Fri 23rd Apr 2010 23:54 in reply to "Not the only way"
Thom_Holwerda Member since:

Microsoft should've provided a software interface to tap into, a standardised solution. It's idiotic to expect every OEM to write their own inconsistent bit of code to handle this.

This is Microsoft's fault.

Reply Parent Score: 10

v RE[2]: Not the only way
by tuma324 on Sat 24th Apr 2010 00:08 in reply to "RE: Not the only way"
RE: Not the only way
by AdamW on Sat 24th Apr 2010 04:03 in reply to "Not the only way"
AdamW Member since:

Er, that's the _whole point_. Exactly as you say, having the hardware key generate win+p keycode is the silliest way to do this, yet that's exactly what Microsoft recommends: that's precisely what the bullet point is telling manufacturers to do.

Reply Parent Score: 9