Sorry, the new beta still has bugs on Windows 7 Ultimate 64-bit. All fonts on start menu and task bar buttons get changed for no reason. I am using default DPI settings also. This problem occurs on every single one of my skins, but not on the skins that come with the beta.

All fonts are set to Calibri, -12, Bold.

Going back to 10.46...

One thing I noticed with the previous beta and this latest update is using Chrome on Win 10 and mousing over the Min/Max/Close buttons, a thin black vertical bar appears on the left side of the window.

Tom is correct. I rolled back to previous WBlind version to compare and found that the latest Beta does indeed randomly change the font for many skins. Since I'm using Win7 x64 and the version 10.4.5 seems to function flawlessly for my particular build, I guess I'll stick with this until issues can be addressed and corrected in new beta.

--Ace--

Quoting LightStar,

reply 29

Sorry, the new beta still has bugs on Windows 7 Ultimate 64-bit. All fonts on start menu and task bar buttons get changed for no reason. I am using default DPI settings also. This problem occurs on every single one of my skins, but not on the skins that come with the beta.

 

All fonts are set to Calibri, -12, Bold.

Reduced 60%

Original 987 x 437

 

Going back to 10.46...

Is that perhaps the right font, but simply the wrong size.  Many changes were made to handle mixed dpi and so that might be whats going on there.

I would recommend you have a quick look in case anything else jumps out at you so we can address the issues in one go.

I suspect many of the issues will be specific to Windows 7 as many of the new features are targeting Windows 10 and so the build will have been tested further on that OS (more testing on the other OSes later for final release)

Quoting Neil Banfield,

reply 35

Quoting LightStar,

reply 29

Sorry, the new beta still has bugs on Windows 7 Ultimate 64-bit. All fonts on start menu and task bar buttons get changed for no reason. I am using default DPI settings also. This problem occurs on every single one of my skins, but not on the skins that come with the beta.

 

All fonts are set to Calibri, -12, Bold.

Reduced 60%

Original 987 x 437

 

Going back to 10.46...

Is that perhaps the right font, but simply the wrong size.  Many changes were made to handle mixed dpi and so that might be whats going on there.

I would recommend you have a quick look in case anything else jumps out at you so we can address the issues in one go.

I suspect many of the issues will be specific to Windows 7 as many of the new features are targeting Windows 10 and so the build will have been tested further on that OS (more testing on the other OSes later for final release)

No Neil, it is the correct font and the correct size, verified in SKS 10. It does it on all my skins, and I checked many of them in SKS 10. The settings are correct, the execution is not. In 10.46 beta, all is fine.

I am afraid to even install the beta on Windows 8.1 and 10.

Thanks for testing Ace, hope they can fix it. 

What do you mean by "Font is being deleted" Neil? It is a Windows 7 system font. 

I don't have any fonts added to the skin at all in the fonts area in SKS 10.  No need to if the font is a system font, and besides, if you add a font to a skin and later decide you don't want that skin any more and delete it in WB, the skins folder still remains in the Windowblinds directory, because of the fonts. Only way to delete the folder is to reboot and then manually delete it.

That is why I do not add unnecessary fonts to a skin.

Quoting LightStar,

reply 41

What do you mean by "Font is being deleted" Neil? It is a Windows 7 system font. 

 

I don't have any fonts added to the skin at all in the fonts area in SKS 10.  No need to if the font is a system font, and besides, if you add a font to a skin and later decide you don't want that skin any more and delete it in WB, the skins folder still remains in the Windowblinds directory, because of the fonts. Only way to delete the folder is to reboot and then manually delete it.

 

That is why I do not add unnecessary fonts to a skin.

What you are thinking of a font, I am thinking of as a font file.

A font to me is the in memory instance of that typeface in a specific size.  WindowBlinds would appear to have deleted its in memory copy but trying to use it still.  So you get either default OS font (on your taskbar buttons) or in the case of the start menu a generic sized and face font which is bigger.

Quick update to this : The problem has been found and fixed.  It only impacted the font object assigned in the StartMenu.ButtonBackground section.  I imagine your skins are using the same font object in WB and that's why the problem spread to more areas.

Quoting LightStar,

reply 44

Quoting Neil Banfield,

reply 43

Quoting LightStar,

reply 41

What do you mean by "Font is being deleted" Neil? It is a Windows 7 system font. 

 

I don't have any fonts added to the skin at all in the fonts area in SKS 10.  No need to if the font is a system font, and besides, if you add a font to a skin and later decide you don't want that skin any more and delete it in WB, the skins folder still remains in the Windowblinds directory, because of the fonts. Only way to delete the folder is to reboot and then manually delete it.

 

That is why I do not add unnecessary fonts to a skin.

What you are thinking of a font, I am thinking of as a font file.

A font to me is the in memory instance of that typeface in a specific size.  WindowBlinds would appear to have deleted its in memory copy but trying to use it still.  So you get either default OS font (on your taskbar buttons) or in the case of the start menu a generic sized and face font which is bigger.

 

In that case, I have absolutely no idea what you are talking about. I have no way of knowing if the beta is deleting a font in memory. 

I have updated my post as it is now fixed.  It was indeed getting deleted from memory in error.

Quoting LightStar,

reply 46

Sweet! I will give it another try, thanks Neil. 

OK, I guess the fixed store download is not there yet, still doing the same thing. 

 

Back to 10.46. all is well.

By fixed I mean internally fixed.  We have not updated the build and will not until next week.

It's great to hear that the problem has been identified and resolved. Will look forward to the updated version release next week. Thank-you Neil & Stardock team.

-- Ace --