I think they're a plus, but I'd like to see it explained what they revert to, and since some settings only take on program restart, I think it'd be even more useful to have a comparison matrix for factory, reversion and pending change.

disclaimer: I used to be involved with TV set-top box UI development. Some of them used to have pretty deep menu structures that some customers would get lost in. After deciding that they're experienced users, if not actual experts, and changing settings, they'd lose the channels that their installer or retailer had downloaded for them. Then they'd decide that stabbing a 'defaults' option was a reasonable thing that any expert user would do to recover them. Then they'd ring us, declare that the STB was crap and had stopped working arbitrarily, screw us around denying that they'd touched anything, and then blame us because the menu tree was too complicated or too simple, or too whatever, but never that it was simply giving them way too much credit to offer an option and expect them not to arbitrarily change it, even if they didn't know what the hell it was supposed to do. They're power users, and that's what power users do.

Oh dear. That's a slightly embittered rant, innit? The point stands, though.

My point is ... rationalise (or indeed rationalize if you wish)

But get rid of stuff that's not used 99% of the time - so designers and engineers can see a clear line to getting their work done

The only one of these buttons which even makes a case to justify it's existence is the last - all the rest are Kruft !

I want to see Tim STOP development on V9 and do what Apple did with Snow Leopard (I Think it was) - and has paid them bountifully ever since !!

... S T O P A D D I N G N E W S H I T ...

... A N D M A K E T H E S H I T W E H A V E B U L L E T P R O O F !!