Nakor

WindowBlinds 10.70 beta1 available

▼

WindowBlinds 10.70 beta1 available

from Stardock Forums

http://storage.stardock.com/files/beta/WindowBlinds10.70_beta1_setup_sd.exe

Adds: Blur is now acrylic blur for recent versions of Windows 10
Fixes: Some Explorer windows not being sized correctly
Fixes: Taskview on Apr build of Win10
Fixes: Firefox skinning
Fixes: FF not resizing correctly after a fullscreen video
Fixes: VS2017/2015 crash issues
Fixes: Some QT5 based apps not sizing correctly
Fixes: Perforce client
Fixes: DXDiag sizing issue
Fixes: Secondary taskbar not showing the clock
Known issue: Groupy tabs paint incorrectly on Office apps on Windows 8.x with WindowBlinds running

windowblinds
238,147 views 59 replies
Reply #26 from Stardock Forums Top

Quoting RedneckDude, reply 23


I changed all the button text states to white and now it works, but if I used large buttons, (which I don't) it would look terrible on the buttons.

Which theme are you referring to? Large Buttons?

Reply #27 from WinCustomize Forums Top

It is an unreleased theme so far.

 

Quoting basj, reply 26

Large Buttons?
I mis spoke, although there is a setting to use small taskbar buttons in Windows.  I meant to say if I had text showing on my buttons it would look terrible in white.

 

 

Galactic Civilizations IV
Reply #28 from WinCustomize Forums Top

It's also not the only theme that does this.

Reply #29 from Stardock Forums Top

Quoting RedneckDude, reply 28

It's also not the only theme that does this.

Yes, it more apparent if you have dark text on dark taskbar backround or white text on white taskbar BG.

 

Reply #30 from WinCustomize Forums Top

Quoting basj, reply 29

Quoting RedneckDude,
reply 28

It's also not the only theme that does this.



Yes, it more apparent if you have dark text on dark taskbar backround or white text on white taskbar BG.

 

As you can see from my pics in reply #7, both taskbars from same skin. It is supposed to be white text on dark background, but it isn't showing up that way.

Reply #31 from Stardock Forums Top

VLC 3.0.3 is still buggy with WB skinning: the right side and bottom edge become corrupt once you start resizing the application (black lines get drawn). Also this causes duplication of some buttons.

Also, once Firefox is enabled in WB you lose all possibility of skinning it via UserChrome.css as each time this file is overwritten by WB, reverting whatever changes you make there.

Reply #32 from Stardock Forums Top

Quoting RedneckDude, reply 30


 
As you can see from my pics in reply #7, both taskbars from same skin. It is supposed to be white text on dark background, but it isn't showing up that way.

Yes Jim, I understand what you're pointing out. I am not saying, I am okay with it. I do hope it get fix when it goes out of beta.

Reply #33 from Stardock Forums Top

Quoting gvse, reply 31

VLC 3.0.3 is still buggy with WB skinning: the right side and bottom edge become corrupt once you start resizing the application (black lines get drawn). Also this causes duplication of some buttons.

Also, once Firefox is enabled in WB you lose all possibility of skinning it via UserChrome.css as each time this file is overwritten by WB, reverting whatever changes you make there.

On VLC 3.0.3, yes I see it too.

On Firefox. My personal take on it is.. you should not have two skinning property running at the same time. Obviously one will get over written by another if it clash. of Worst it will crash firefox.

Basj,

Stardock Community Assistant

Reply #34 from WinCustomize Forums Top

Quoting gvse, reply 31

Also, once Firefox is enabled in WB you lose all possibility of skinning it via UserChrome.css as each time this file is overwritten by WB, reverting whatever changes you make there.

Hi gvse,

Go to C:\Program Files (x86)\Stardock\WindowBlinds folder. Find the file ff.css (this is a file that replace your UserChrome.css in Firefox Profile folder).  So open it in any text editor, insert your css code and finally overwrite it. Then restart Firefox and enjoy! |-) Similarly you may edit the th.css file for Thunderbird.

Look at the result (this is Firefox Quantum 60.1.0esr):

 

+1 Loading…
Reply #35 from Stardock Forums Top

Thanks a lot Vad_M!

This actually works!

I do have one issue left: how did you solve the problem of min/max/restore titlebar buttons in firefox? Mine are just gone when I apply the wb code

Code: css
  1. #main-window { -moz-appearance: -moz-win-glass !important;} #titlebar-buttonbox > toolbarbutton { opacity: 0.0 !important; }

I mean the native WB titlebar doesn't get applied to my skin. It must be something in my FF css, but I am at a loss what it could be.

Anyways, thanks again for the tip!

Reply #36 from WinCustomize Forums Top

Here is my code for Windows 10:

Code: css
  3. window:not(:-moz-any([id*="alert"],[id*="popup"])) {-moz-appearance: -moz-win-glass !important; background: transparent !important;}
  5. #main-window:not([tabsintitlebar])[sizemode="maximized"] {padding: 3px 0 0 0 !important;}
  7. #main-window:not([tabsintitlebar])[inFullscreen] {margin: 0 !important; padding: 0 1px 1px 1px !important;}
  9. #main-window[inFullscreen] #nav-bar {display: none !important;}
  11. #titlebar {margin: 0 !important;}
  13. #titlebar *, #fullscr-toggler, #navigator-toolbox:before, #navigator-toolbox:after, #nav-bar:before, #nav-bar:after {display: none !important;}

But if you still see the opaque rectangle at the top right of maximized window - this is a problem with your graphic adapter. Just disable hardware acceleration in Firefox Options and the problem will be solved. :)

P.S. By the way the Firefox titlebar text is visible only if I move the mouse cursor over the titlebar buttons. Otherwise it dissapears... This is WB bug on Windows 10. (On Windows 7 all works fine!)

Reply #37 from WinCustomize Forums Top

I got fed up with SD because of the VS2017 crash issue and uninstalled all SD skin products. This beta fixes the VS2017 crash, but there are still a couple of skin issues.

1: The start and the hidden systray buttons are being properly skinned, but most of the task bar and system tray are not being skinned, just basic black. The clock is not readable unless I hover the cursor over it, then it is just barely readable. I tried several skins including Stardock Design released ones and they all have this issue.

2: the WB systray icon still won't stay put across reboots. I move the icon to a specific location in the systray, but when I reboot it is moved back into the hidden area. Yes, I can get to it, but this icon is the ONLY one that won't stay put across reboots. This may seem like a trivial complaint, but it shouldn't be that difficult to fix!

Reply #38 from Stardock Forums Top

Quoting kkunderwood, reply 37

I got fed up with SD because of the VS2017 crash issue and uninstalled all SD skin products. This beta fixes the VS2017 crash, but there are still a couple of skin issues.

1: The start and the hidden systray buttons are being properly skinned, but most of the task bar and system tray are not being skinned, just basic black. The clock is not readable unless I hover the cursor over it, then it is just barely readable. I tried several skins including Stardock Design released ones and they all have this issue.

2: the WB systray icon still won't stay put across reboots. I move the icon to a specific location in the systray, but when I reboot it is moved back into the hidden area. Yes, I can get to it, but this icon is the ONLY one that won't stay put across reboots. This may seem like a trivial complaint, but it shouldn't be that difficult to fix!

Hello,

Could you please show us your problems with screenshot. I am trying to understand your problems. Please use the SD skin so I also can see it on my system.

Thank you,

 

Basj,

Stardock Community Assistant

Reply #39 from WinCustomize Forums Top

I have a PNG screenshot of the taskbar and systray, but there doesn't seem to be anyway to paste it into this reply.

Reply #40 from Stardock Forums Top

Quoting kkunderwood, reply 39

I have a PNG screenshot of the taskbar and systray, but there doesn't seem to be anyway to paste it into this reply.

Try this site to upload your image https://imgur.com/upload

 

Reply #41 from WinCustomize Forums Top

Won't the insert/edit image button handle a .png image?

Reply #42 from WinCustomize Forums Top

Quoting Uvah, reply 41

Won't the insert/edit image button handle a .png image?

Yes but not all members have access to that button.

Reply #43 from WinCustomize Forums Top

Oops! Sorry, didn't see your post above. My bad. :blush:

Yup, handles a .png. He can upload his image this way.

Reply #44 from WinCustomize Forums Top

Quoting Uvah, reply 43

Yup, handles a .png. He can upload his image this way.

You have to be at a higher level than he is to have access to the image upload button.

Reply #45 from WinCustomize Forums Top

As I stated in my initial post I had uninstalled all SD skin products including Start10. Instead I installed the open source "Classic Start Menu" which I consider far superior to Start10 in functionality and flexibility. Anyway this was causing a skinning conflict so I have uninstalled the WB beta.

Reply #46 from Stardock Forums Top

I've experienced another problem: when using 2 displays via Project/Extend commands in win10 the taskbar on my main display becomes non-responsive (buttons don't react to clicks), and it disappears almost completely from the secondary/extended screen (only the "TaskView" button is visible).

Im on Windows 10 Home (17134.rs4_release.180410-1804)

Reply #47 from Stardock Forums Top

Quoting gvse, reply 46

I've experienced another problem: when using 2 displays via Project/Extend commands in win10 the taskbar on my main display becomes non-responsive (buttons don't react to clicks), and it disappears almost completely from the secondary/extended screen (only the "TaskView" button is visible).

Im on Windows 10 Home (17134.rs4_release.180410-1804)

Hello,

Sorry to hear you are having issues. Please try the purge and reinstall steps : https://forums.stardock.com/486023/windowblinds-support-faq#reinstalling

Reboot, retest and report back.

Thanks.

Basj,

Stardock Community Assistant.

 

Reply #48 from Stardock Forums Top

I already installed the update after going through the purge routine so there's not much more I can try.

I had to revert now to the stable installation as working with a secondary display was proving too troublesome.

Reply #49 from Stardock Forums Top

I would like to remind you/mention that for many users of the new FireFox, userChrome.css is the only method of changing the user interface and your beta still overwrites the user defined edits in that file.  Would make more sense to APPEND your adds to the end instead of overwriting my changes.  For those that have this problem just rename "ff.css" in the stardock/Windowblinds folder to something else.

Reply #50 from Stardock Forums Top

That seems to fix FF not closing reacting on the close sign for now thx :)

 

edit : still bit laggy on closing tho :P