WindowBlinds 11 planning
Friday, December 25, 2020 by Frogboy | Discussion: WindowBlinds
We are putting together the schedule to make WindowBlinds 11.
Customization is a lot harder now than it used to be. 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.
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.
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.
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. Keep in mind though, the more non-standard apps we have to handle, the harder it is for us to keep compatibility.
Earlier this year we released Curtains which doesn't even hook into the OS. This means it is 100% compatible. Skins, even the weirdest ones, won't break a given app. 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.). It's done quite well. 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.
That's where this thread comes in: What would you like to see in WindowBlinds 11?
 |
|
Page 2 of 34 | |
|
|---|
Reply #22 Tuesday, February 2, 2021 10:52 AM
I don't know if it has to do with Fluent Design but, anything higher than Build 21255 has really f*cked up WB!!!
How MS can fubar a perfectly decent OS in one fell swoop is beyond me!!!
(Sorry for the language but, it really p*sses me off!!!)
WB is not compatible with Windows 10 21H1
Reply #23 Tuesday, February 2, 2021 10:53 AM
Please work on skinning Edge titlebar.
All browser on Chromium is compatible with WB.
Reply #25 Tuesday, February 2, 2021 12:11 PM
I don't know if it has to do with Fluent Design but, anything higher than Build 21255 has really f*cked up WB!!!
How MS can fubar a perfectly decent OS in one fell swoop is beyond me!!!
(Sorry for the language but, it really p*sses me off!!!)
WB is not compatible with Windows 10 21H1
All browser on Chromium is compatible with WB.
Reply #26 Tuesday, February 2, 2021 12:29 PM
Not on my machines. I’ve been trying to get to work for 2 years now.
WB works correct on Edge Chromium, but you must add this:
--disable-features=Windows10CustomTitlebar
--disable-windows10-custom-titlebar
Reply #28 Tuesday, February 2, 2021 2:08 PM
Reply #30 Tuesday, February 2, 2021 2:32 PM
So, basically what you're saying is that when it works for you, it must work for everybody else? Go trolling somewhere else.
I have tested these settings on many Windows 10 computers and it works. Apparently you can't do such a simple thing.
Reply #32 Tuesday, February 2, 2021 5:08 PM
Reply #33 Tuesday, February 2, 2021 5:10 PM
Reply #34 Tuesday, February 2, 2021 5:56 PM
I already know about this. Doesn’t work for me.
If it doesn't work for you, you are doing something wrong.
Reply #35 Tuesday, February 2, 2021 8:39 PM
Guess I'm in the middle then... it only works partway for me, when it wants to.
When I first open Edge, with the (--disable-windows10-custom-titlebar) fix applied, it opens like this;
If I then MIn/Max the window, or click elsewhere on the desktop, then back into Edge, it then redraws the titlebar fully to this;
Chrome does the same thing, as does Brave browser.
Vivaldi and OperaGX just refuses to skin at all.
I'd be willing to bet that skinning ANY browser is going to be problematic, as you're always coding against a fast-moving target.
Reply #36 Tuesday, February 2, 2021 9:03 PM
Hello,
Well, Edge work for me too. And I don't have issue as mentioned by GAIAStevef above. Might need to look into extension/add-on compatibility too. My Edge is running without any extension at all.
Thank you,
Basj,
Stardock Community Assistant
Reply #37 Wednesday, February 3, 2021 7:17 AM
I have only Ublock Origin, NoScript, SpeedUp, AutoTab Discard and WB works correct on Edge Chromium and nVidia + Intel config. If somebody has problems maybe some addions or flags has conflict.
Reply #38 Wednesday, February 3, 2021 2:38 PM
If I have Edge open and change a theme it applies. If I close the Edge window and open it up again Win 10 theme titlebar is applied.
Reply #39 Friday, February 5, 2021 5:58 PM
Maybe you fix correct centering in skins ?
Second photo is from Windows skins and First photo is from some WB skins. Some WB skins It doesn't want to align to the left and is shifted right and down.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
|
|
Page 2 of 34 | |
|
|---|
Reply #21 Tuesday, February 2, 2021 10:18 AM
*Large start button support again. I have noticed trying to use the vista style of start orb causes it to get cut off in windows 10.
*Blur added to explorer background like how curtains allows would also be nice.
*Skinning of jumplist/preview list. Startisback++ adds back the ability to use classic jumplist/preview hover images. Im sure you guys could figure out how to get those loaded with windowblinds 11.
*Skin studio to be updated to a new version that only works on windows 10. This would help with those who focus on only windows 10 skinning. There are so many things not used in 10 that would cut down on time skinning if I knew what is and is not on 10.