I think you need to give examples here I am afraid.

My pleasure.

WB

UXTheme:



Both on Windows 11.,

c242

reply 2

My pleasure.

WB



UXTheme:



Both on Windows 11.,

I Think Themes makers and Theme Patchers were much quicker than SD adopting Win 11, that is one of the reasons i moved over to Themes Carl, plus, i could still customize my Desktop the way i wanted too from almost day one with Win 11 using UltraThemePatcher . I remember that topic about WB 11, going on and on, peeps getting annoyed with the wait and some of the Generic "It Will Be Ready When Its Ready" replies.

I do think SD will catch up with Themes sooner or later Carl. I now have Loads of Dark Themes with fully contrasting Fonts colours, a lot of them are even more clearer than your screenshots Bro, and due to this and other factors, i still have not gone over to Start 11 and back to WBs, no need when the flip side of the customizing coin does all i need.

As usual before Doc jumps on me from a great height Ha Ha  

Usual Disclaimer

Themes and patchers can leave you with a Black Screen if not used correctly and done in the right way, and can void any warranties. If you want the easier option to customize your set up, go with Stardock, as i am sure it will catch up to Theme and Patcher creators using Win 11 in the near future.

c242

reply 2

My pleasure.

WB



UXTheme:



Both on Windows 11.,

Whats funny is that font was white at some point in one of the betas for Windowblinds11 early on. When It fully came out of beta it was stuck black again.

Yes, See how long I have been talking bout this. If we get this one back, I could finally use WB again. And I guess other dark mode lovers too. It has been too long.

And a way to get the search box text to be white when I dark mode. There are just to many black fonts that make it hard to design fully dark mode themes that windows natively can do without windowblinds applied.

Is WB set to automatically adjust a skin for dark mode and is the OS actually set to dark mode?

Both YES for me when I last tried.

Yes it does not matter what settings you set. That font remains black on all theme. It did change to white in the past in early test builds of windowblinds 11. I don't remember what ones but it was right when the darken ui elements function was added when it was working correctly. Both windows 10/11 pretty much are the same with this issue.

Thanks Simplex for helping with this. As a wb-skinner You have even more insights.

Hello Naroon, hope you are doing well.

In many ways Windows 11 was a late bloomer. I think Windowblinds 11 really did suffer because of this, not because themepatcher is better but because the changing design of Windows 11 was hard to catch up to when using Windows 11 parts. In many ways it is too bad that we only have a short window to enjoy a more finished version of Windows 11 before Windows 12 drops... But Windows 12 may be exactly what is needed for stardock to return to form with customizing a pc. The one thing I am hopeful for is that we can come up with a clear vision as to how we all want the explorer skinned.. 22h2 and the explorer tabs is the wrench that got thrown into windows 11 skins that maybe never got fully corrected (explorer tab changes also broke the dark themes if I remember correctly). If that problem gets figured out, on a popular level, I think Windowblinds will be much more successful.

So, we all wait for the next Windows to eventually be able to fully use WB again? I don't want to believe that. Also a lack of documentation makes it really hard to begint skinning WB or even looking things up in the 1st place. It went to complicated to just figure out how to do a WB skin only from other skins. The latest tutorial I could find is from 2007. 

I hope not, hopefully I am just getting ahead of myself as to what Windowblinds 12 can bring. I would like to believe that Windowblinds 11 has at least one more update left before we start to think about Windowblinds 12.

Very true. I remember back when I was testing Windowblinds 11 my top desire was to be able take old windowblind skins and make them match Windows 11's explorertabs.

Here is my problem, (and this is based on what I am observing on the forums here) I think that out of all Windowblinds 11 users only about 3 - 5 percent of those that are using this program even know how to take an old skin and put the new windows 11 parts in its place to have a skin updated for Windows 11 vs 10. Truthfully, I feel the amount of people that should know how to do this should be at least 50 - 60 percent. There are many ways this could be achieved and I would be happy with any of them.

I didn't mean to hijack your thread. I do believe the original post deserves consideration for a future update of Windowblinds 11 for sure 

Hi PheonixRising1 , i too wish you are well.

As you know, i was one of those who would have preferred WB 11 to be released earlier than it did so i could of stayed with SD Software, and was also one of those that said WB 11 would suffer due to the time after Win 11s release, we actually got it. I know SD did not want to ship it too soon, but even when we did get WB11 and Start 11, those "Report Issues" Topics with both, throwed up multiple issues which put me off using it, and as we are here in this Topic discussing an issue which still has not been sorted out all these months later, i have zero motivation to re adopt SD Programs. Themes were more on the ball, as it was possible to customize Win 11 almost from the Start, and gave many updates to try and counter Win 11 Explorer changes and other changes that were present at those times.

I think Carl is right, and should have expected the font issue to be fixed a long time ago. I have never had this issue with Themes, they contrast each other easily and do what is wanted from them out of the box so to speak. If you would have told me , i would after a short time remove WB11 and Start 11 from my Computer, i would have told you, you were crackers, but here we are and Themes with StartAllBack and UltraThemePatcher are my go to method for fully customizing my set up, Why, Simply put They Work and give me No Issues.

I have not given up with SD apps, that is why i am still a member, (after all, i do still own copies of WB11 and Start11) so have paid the Entry Fee, so to speak. But until those products can match what i have with Themes and Patchers, i have to stick with what works how i want them too, and right now, that is still not WB11 and Start11. Really looking forward to Win 12, maybe Win 12 will be the Making of SD Apps and they can sort out the issues we read about in the forum, i for one hope so.

Here's something more recent: "Roan" by Po' creating a skin, step by step together with 2of3:

https://forums.stardock.com/417268/page/1/#replies

With links to more.I'd hunt more but I'm occupied atm.

Also, Vampothica published on skinning:

https://forums.stardock.com/383174/page/1/#2634533

A shame the Win Wiki was lost.

I do think at this point it is fair to say that maybe start 11 is the software that got all of the time and energy in regards to development time all through Window's 11's lifecycle. To be fair, I also believe that start 11 needed the major overhaul that it received. Start 10 was starting to feel quite dated, start 11 on the otherhand feels very modern and a worthy start menu replacer. Unfortunately, not all major releases are equally major. I do not believe Windowblinds 11 ever had the development time for the same major overhaul that start 11 had. The reason for this is because Neil's team develops for multiple softwares and most likely only has time for one major overhaul per every several years.

With that said, I also do hope that Stardock doesn't pigeonhole itself into being a start menu replacer by releasing as many start program version as possible at the expense of a major over haul that is much needed for Windowblinds 12. I truly believe that it is Windowblinds turn to have a six month plus window of development (major overhaul window). Neil's team can do some great things in that time frame. I do know that start 11 or 12 sell very well and it is very tempting to stay developing it to make money. But for the sake of OD subscriptions and having a good portfolio of software a risk somewhere else is needed. I believe that risk should be with Windowblinds because of the community it carries. That of course would have to happen as Windowblinds 12 on Windows 12.

I agree with you PheonixRising1. WB 11 or 12 does need some much needed attention, maybe if it got that and worked out of the box so to speak, i and others would come back to SD.

Hi Carl, i did also check out those links and thought exactly the same as you, guides over 13 plus Years old, surely can not be of any use, for products released over a Decade Later?

So, this is it (again)? Even no answer to my question?

I will give you the best answer I can.

As pointed out by SimplexDesigns your issue is in fact a bug that requires an update. If your issue could be fixed without an update I am sure Neil would have chimed in already. His silence likely means it does require an update and updates are authorized by someone else (i.e. Brad)

My opinion on the subject is that all software should receive one last update and bug squashes as we wait for Windows 12 to be released. It could happen but Neils team usually only works on one software at a time and it looks like they are still busy with start 11. Unfortunately we are now at wait and see.