That's where this thread comes in: What would you like to see in WindowBlinds 11? However, we know there are still plenty of people out there who would like to have more full control over how their Windows desktop looks. Of course, the price is that it doesn't skin nearly as much (no client area GUI controls like scrollbars, push buttons, radio buttons, etc.). Skins, even the weirdest ones, won't break a given app. Keep in mind though, the more non-standard apps we have to handle, the harder it is for us to keep compatibility.Įarlier this year we released Curtains which doesn't even hook into the OS. Still, with that in mind, there are things we can do such as skin the standard OS controls and then handle apps on a case-by-case basis. Which is unfortunate because WindowBlinds, in theory, could actually give Windows users a consistent, OS-wide Fluent if apps weren't handling the drawing of their own UIs these days. Microsoft's baffling decision to throw away trying to provide a standard set of in-app controls for developers and instead provide vague, often conflicting standards (cough, Fluent) has resulted in having less and less of the OS we can even touch. Microsoft, for reasons unknown, has actively encouraged developers to take care of their own client and even non client (border, frame) painting rather than using standard Windows controls.

We are putting together the schedule to make WindowBlinds 11.Ĭustomization is a lot harder now than it used to be.

What is stardock deskscapes