Comment by nolok | Hacker News Reader

Comment by nolok | Hacker News Reader

Parent Full thread

I know it's not really the subject here but I've faced a weird case of "what why ?!?" about a windows driver thingy and it's been on my mind to share it for a couple weeks now

For some weird reason, the package to handle the very generic Synaptics touchpad on both my Asus and MSI laptop was moved out of the driver (+ included config panel to configure it), to a combination of a driver that does stuff but you can't configure, and an obscure windows store app that isn't installed with the driver, and is now the only way to configure it.

Want to disable your touchpad when an usb mouse is connected, remove tapping (quick tap on touch pad = left clic), set up multi touch gesture and whatnot ? Well then you better know that you need that, because there was no indication whatsoever that they removed it from the driver, the panel just disappeared over night (oh and it doesn't keep your old settings either, although in my case it was a plus since that's how I knew something changed).

And windows store search is so miserable that searching for "synaptics" does not bring up the app, and it doesn't show in the windows store "my library" listing.

If anyone is involved in that, I would buy you a beer or three just for the chance to sit in front of you and listen to how that happened (this offer of course extends to anyone on the skype team who can tell me the story of how skype continually gets worse at being a chat app)

See this for an overview of the design guidelines--part of which is to break out app functionality: https://docs.microsoft.com/en-us/windows-hardware/drivers/de...

This is almost certainly motivated by the push to start selling devices in S-mode (aka, Windows Store-only mode). Though generally-speaking, when you have hardware with Store apps that configure them, Windows is supposed to (and generally does from my experience) automatically install the app, rather than have you look for it.

Having apps running in sandboxes where they only have permission to talk to the device they're built to interface with is more secure, and arguably, the best choice for most non-technical users. I'm glad this is the direction they're moving, as long as the ability for those of us who need it to turn such protections off remains.

Makes sense to me; and I genuinely approve of the intent, but why

- is it not installed when the driver installs (to be clear: if you have the app installed, then in the "mouse properties" control panel you have a new tab that appears called "device settings", it's not an app that you launch on its own, it's not a new control panel, it's at the same spot as before as a tab in a generic windows control panel, there is no placeholder to warn you ... it's a really bad experience)

- was I not warned about it when it moved me from the older/legacy one to that (by windows update)

- can't I find it in windows store search or in my library of installed app (only way to find it to install it that I know of, is to open the direct link in edge and let edge pass it to the windows store app) [if that one is me being an idiot, I will gladly take it; because it's the weirdest one for me]

- did it not carry over my settings (I noticed it because both tapping and disable-if-usb reverted to default settings)

It felt like one of those case where they all played with the "new install" experience and no one took looked at what users doing an update would see.

It's a great move forward, and a great idea, but a terrible user experience. 10 minutes in a beer testing environnement would have told them that.

Microsoft probably had little, if anything to do with the decision. Synaptic put a new driver through the pipeline that ends with it being pushed through Windows Update as part of the normal keeping your drivers updated goal (from Microsoft's perspective). There's a lot of QA that goes into that process , but it's all on the "can this driver take down the system, or only the device it's written for?" It's on Synaptic to make good UX choices for the software they distribute, driver config tools included. And it's on ASUS and Msi to select hardware with stable, quality drivers and config tools.

Getting to sit down and talk with the guys that made those decisions would be pretty great, but it's not Microsoft you're really interested in talking to here.

Reply on news.ycombinator.com