I haven't been on Insider builds for a while. When 1703 releases I'll take a look at it.

This is amazing, thanks so much.  Should be stickied in the forum!

Cheers!

Stickied

I think the caption text is controlled by Windows itself as it'll change from black to white depending on the background color, I'm not sure if you can change it from the msstyles or not.

I doubt GDIPlus is related to the msstyles directly. Do you use GDI++ or WindowBlinds/WindowFX (I believe these override some stuff in gdiplus though I could be wrong)

I'll see if I can update WSB to allow custom DWM mapping here soon. The problem is that for 8 and onwards I was just using some old porting code which hardcoded the DWM property maps to the newer states. So it was like part x = part y. I should be able to use XML like the other half of the conversion process to make porting easier.

Make sure that no properties are missing under the DWMWindow (Windows & Caption Buttons > Aero > DWM Window) class when comparing your theme to the default Aero. If any properties there are missing, DWM will crash.

I'm not entirely sure if this would be caused by 1.5.6.3 or not since those metrics are just normal properties. You can try changing the caption metrics in Fonts, Colors, & System Metrics > Fonts & System Metrics or change the content margins in the various states under Windows & Caption Buttons > Aero > DWM Window > Controls > Captions > Window

Be careful, most blackscreens are caused by the DWM classes being different. That's why in the beta you can't change them.

I don't think it's possible.

255, 255, 255
#FFFFFF

The color search has to have all three components.

Actually you should be able to do so with a StyleScript:

Code:

<stylescript>
<remove>
<class class="SIB_StartPanelPriv"/>
<class class="SIB_StartPanelComposited::StartPanelPriv"/>
</remove>
</stylescript>

Save that as SIBClassRemove.xml in your WSB\Data\StyleScripts folder and then hold Shift and click Import Stylehack and select SIBClassRemove then click Apply StyleScript.

If you manually remove it from the CMAP WSB will remove the properties on compile. Editing the CMAP requires hex editing though.

What was the error message?

Thank you,
It is no longer possible to modify the Taskbar in Windows 10 final version?

I haven't tried to customize 10 but as far as I know you can't.

They're created using the beta; http://vistastylebuilder.com/forum/index.php?topic=2130.0

It doesn't really support Win10 but it still works.

Editing XAML is easy if you're making your own application, but if you're wanting to customize the built in apps it's probably not going to be easy.

can we expect VSB support for windows 10

the UI is far to white for my liking

will need to be extensivly modded before i can use as a daily driver

What do you mean by Win10 support? To my knowledge the current version works with 10.

Also the UI uses the same parameters as all other Win32 apps, you can change it in Fonts, Colors, & System Metrics > Fonts & System Metrics

I hate those dark jumplists and context menus. Should only be dark if you are using a dark theme.

Microsoft doesn't do consistency.

I feel that may be optimistic, windows controls have been predominately blue for years already anyway.

I'm surprised you can even still change the background of the taskbar to be honest.

One of those might be a mask. I believe in 8 there was the bitmap and then a mask over it for the color animation.

Does this happen with all menus, or just that program?

What was the last property you copy/pasted?

Is UxTheme patched? If you're using UxStyle as a patcher try restarting the UxStyle service.

I'm pretty sure this was in Vista.

The next build isn't going to have a timebomb, it was only there so it would kind of force everyone to be on the same version so I could make sure bugs weren't reoccurring in newer builds. I last spoke to Ave some time ago and he stated that he would create a COM component for creating the msstyles, that would allow me to use .NET to program WSB which would be a lot easier as I have more experience with it. This is also the primary reason I haven't put out a new build in some time.

Are those last two specific to 8?

It's possible it isn't an enabled feature.

Hey mate, thanks for the hard work!  Am I the only one who is experiencing BSOD after applying and saving?  I can test it and it works great but when I save the file and go to use the theme from the personalization options it Black Screens on me?  Any suggestions.

Here's the Windows 8.1 theme I'm working with without the jumplist fix so it should work fine until you apply and save the stylescript.
UNITY 2014 beta https://www.dropbox.com/s/2okrsdhfvq2si1j/UNITY%202014%208.1%20to%2010%20Themes%20Beta.zip?dl=0

Thanks for any help/suggestions.  As always please make a system restore point/create snapshot before using.

What's the BSOD message?

Hi PandaX
We need to find a way to change the inactive text color and the inactive caption buttons of the modern apps.

Regards
Nighthawk-f22

I haven't had a chance to look at the MSStyles for 10 yet but the text color for Metro windows isn't something that's in the msstyles I imagine, considering it changes depending on the colorization color of DWM.

Well for now.

Well at least I don't have to update WSB for Win10 support. Nice work guys!

You can clear out the testing folder, it's supposed to automatically, but can't if it crashes.

This build doesn't prevent a blackscreen, but it'll try to recover from it: http://vistastylebuilder.com/forum/index.php?topic=2130.0

It suspends WinLogon, checks if DWM is running, if not applies Aero and resumes WinLogon (which itself will restart DWM).

UxThemePatcher also doesn't cause the black screens, it's winlogon getting stuck in an infinite loop.

It's not WSB that causes it, it's a bug in winlogon. Whether or not you apply via WSB or with a .theme file is irrelevant as they both apply themes the same way, so it can still happen. Sometimes it can happen just based on where you saved the file, which is why I always either use the desktop or %programdata%

Don't delete the mui files, they're supposed to be there.

Ok, then it might be an issue with that theme. The Common File Dialog (Save and Open) will fail if there's an issue with the Shellstyle.dll, if you copy the Shell folder in Aero's folder (C:\Windows\Resources\Themes\aero\Shell\) into the directory where Obscuro.msstyles in (overwriting the Shell folder that's already there) does it work then?

I'll give it a go now. Remember though, this doesn't seem to just be a problem with Windows Style Builder. If I open Notepad, change my theme to a custom one using the Personalise menu, then try to open or save in Notepad, it breaks there too, without even touching WSB. It doesn't seem to be caused by Windows Style Builder, it's caused by changing the active .MSSTYLES, which is leading me to believe it's a problem with UXStyle or something in that region.

As for the latest build, the exact thing happens. Failed Window Show, 2 Common Dialog, 0 Windows.

Ok well you stated in a previous post it didn't affect Notepad: "Yes, the open and save buttons work as normal in Notepad before and after clicking test theme. When the import, export and save buttons have broken in WSB, they remain working in Notepad."

Does this only happen with the theme "Obscuro" or default Aero as well?

Ok, new build. This one after it fails it should open a new SaveFileDialog. The second one uses copy/paste default template code so it should work (though won't actually save anything yet). If it works I'll track it down from there.