Font Change Failure

[Yaron]

Hello,

I've just started using WSB.

I've copied Windows 10 aero.msstyles, and opened it in WSB.
Windows 10 Light Mode > Taskbar & System Tray > TaskBar > Basic > ToolBar.
I've changed the font to "Tahoma, 8, bold, Quality:NonAntialiased", saved the file and closed WSB.



On re-opening the file in WSB, I see ",0" in the FONT field.


Is that the expected result?
Should I edit the mui or msstyles files with a resource editor?

Thank you.

[3am]

You can't change anything under "inherited Properties"

You have to go where the properties are inherited from (you'll see it in WSB status bar).

In this case it would be at Taskbar & System Tray > TaskBar > Basic > ToolBar

[Yaron]

Hello,

I've just seen your reply.
Thank you. I appreciate it.

I'll test it later.

[Yaron]

Hello again 3am,

Trying to copy the aero ("C:\Windows\Resources\Themes\aero") folder, I get the following Permission messages:



Coping only the allowed content and opening the msstyles file in WSB, the fonts are gibberish and I can't test it.



What's the correct procedure? Should I look for any Font field and change it manually?

Thanks again.

 

[3am]

I get that message copying too but I just let it finish and everything is ok.

I don't know why you are having your font problems. Never saw that before.

Try using the Aero folder in the attached zipfile. The aero msstyle tests, saves, has no font problems etc...for me anyway.

If you still have font problems with this msstyle it must have something to do with your system fonts or default language. Maybe.

[Yaron]

A beginner's mistake: I renamed "aero.msstyles" "Test.msstyles" but forgot to rename the MUI file as well.
I'm getting the correct/expected fonts now.

I suppose there's no way to replace all instances of "Segoe UI" with "Tahoma", is there?

Thank you very much. I appreciate your patience.

[3am]

This only works with msstyles already saved in WSB.

Open the msstyle in a resource editor
Go to String > Neutral
You'll find every font instance in your msstyle and you can change them all in one place
Save the msstyle

[Yaron]

I've spent quite a few hours on this.
A lot of black screens. :)

Here are the exact steps:
1. Opened the theme in WSB.
2. Changed either some images or the fonts under "Fonts, Colors, & System Metrics".
3. Saved the the theme and exited WSB.
4. Opened the msstyles file in Restorator 2018 and replaced every instance of "Segoe UI" with "Tahoma" NonAntialiased, saved and exited.
5. Reopned the theme in WSB.

Here is the interesting result:
Testing the theme in WSB, it seems to be working properly: all the fonts are "Tahoma" NonAntialiased.
If I stop testing, modify anything and save - WSB asks if I'd like to use the theme. Selecting "Yes", I get an error: "The theme can not be applied".
Applying the the theme via Windows Settings, I get a black screen.

Thank you. I appreciate your help.

[3am]

Is your theme folder in C:\Windows\Resources\Themes?

Do you have a .theme file ready for your theme in the same place?

[Yaron]

Yes to both.

I actually get a black screen without editing the file in Restorator.

Coping the Aero theme, modifying it in WSB, saving and applying the theme (either via WSB or Windows Settings)  - all is well.
Opening the theme again in WSB, applying any change and saving - the theme gets corrupt and I get a black screen.

It might have to do with some REG files I'm using. But reverting those REG changes (and signing out/in) does not solve the problem.
I'm attaching the theme, the images I've replaced and the REG files.

***

Exact steps:
I've changed the fonts in "Fonts, Colors, & System Metrics".
I've changed the font in "Taskbar & System Tray > TaskBand > Basic > TaskBand".
I've changed the images according to your instructions in https://www.vistastylebuilder.com/forum/index.php?topic=2559.msg14618#msg14618.
I've changed the image in "Explorer & Shell > Explorer > CommandModule > BackgroundShineLayer".
I've changed the image in msstyleEditor Menu > BARBACKGROUND (couldn't find it in WSB :) ).
(The problem exists after reopening the theme in WSB regardless of the last change in msstyleEditor).

Thank you very much.

[3am]

I don't know what to tell you.

I never work directly on a theme I am using. I work on a copy.

I never apply a theme using WSB. That was always hit and miss right from the start.

I always apply a default windows theme before applying a custom one

Sorry I can't be of more help

[Yaron]

I've made some progress. :)

I edited the MUI file in Restorator, opened the theme in WSB, modified it and saved.
Now - applying the theme via Windows Settings, I get the fonts and the (very initial) look I want.

The problem is I can not modify the theme again in WSB.
It's either all changes at the first session or using msstyleEditor. I suppose the latter does not change the fonts and thus the theme doesn't get corrupt.
A beginner's theory. :)

You've been very helpful and kind. Much appreciated.

***

Tomorrow I won't be by my PC, but I'll update later if there are any news.

[Yaron]

I've figured it out.

Copying the default Aero folder, a VSCache folder is copied as well.
On first modifying and applying the theme, the original hidden MSS files are replaced with a new file corresponding to the new msstyles file.
On modifying the theme again and saving it to the same folder, the MSS file is NOT updated. This causes a conflict which results in a black screen.

Solution: Delete the VSCache folder. When your theme is complete (i.e. all modifications are done), copy the Aero folder again (including VSCache), replace the msstyles file and after applying theme - the MSS and msstyles files should match.

Thank you.