Cart Search
New Topic
Forum Home | Login
We have re-enabled logins for the forums, please be aware that you may need to reset your password or register for an account again while we continue to restore full functionality.

WindowBlinds 10.70 beta1 available

windowblinds
3 Pages1 2 3 
Nakor
basj
Join Date 03/2001
+1603 sdemployee
Reply #26 July 19, 2018 9:05:36 AM
from Stardock ForumsStardock Forums

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?

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
RedneckDude
Join Date 04/2009
+2210
Reply #27 July 19, 2018 9:16:17 AM
from WinCustomize ForumsWinCustomize Forums

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.

 

 

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
RedneckDude
Join Date 04/2009
+2210
Reply #28 July 19, 2018 9:17:04 AM
from WinCustomize ForumsWinCustomize Forums

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

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
basj
Join Date 03/2001
+1603 sdemployee
Reply #29 July 19, 2018 9:34:09 AM
from Stardock ForumsStardock Forums

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.

 

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
RedneckDude
Join Date 04/2009
+2210
Reply #30 July 19, 2018 3:36:53 PM
from WinCustomize ForumsWinCustomize Forums

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.

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
gvse
Join Date 10/2007
0
Reply #31 July 20, 2018 4:18:12 PM
from Stardock ForumsStardock Forums

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.

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
basj
Join Date 03/2001
+1603 sdemployee
Reply #32 July 20, 2018 7:57:18 PM
from Stardock ForumsStardock Forums

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.

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
basj
Join Date 03/2001
+1603 sdemployee
Reply #33 July 20, 2018 8:09:34 PM
from Stardock ForumsStardock Forums

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

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
Vad_M
Join Date 08/2004
+117
Reply #34 July 20, 2018 9:18:03 PM
from WinCustomize ForumsWinCustomize Forums

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
Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
gvse
Join Date 10/2007
0
Reply #35 July 21, 2018 4:43:38 AM
from Stardock ForumsStardock Forums

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!

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
Vad_M
Join Date 08/2004
+117
Reply #36 July 21, 2018 5:51:46 AM
from WinCustomize ForumsWinCustomize Forums

Here is my code for Windows 10:

Code: css
  1. window:not(:-moz-any([id*="alert"],[id*="popup"])) {-moz-appearance: -moz-win-glass !important; background: transparent !important;}
  2. #main-window:not([tabsintitlebar])[sizemode="maximized"] {padding: 3px 0 0 0 !important;}
  3. #main-window:not([tabsintitlebar])[inFullscreen] {margin: 0 !important; padding: 0 1px 1px 1px !important;}
  4. #main-window[inFullscreen] #nav-bar {display: none !important;}
  5. #titlebar {margin: 0 !important;}
  6. #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!)

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
kkunderwood
Join Date 10/2003
+10
Reply #37 July 21, 2018 10:49:30 AM
from WinCustomize ForumsWinCustomize Forums

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!

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
basj
Join Date 03/2001
+1603 sdemployee
Reply #38 July 21, 2018 11:00:59 AM
from Stardock ForumsStardock Forums

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

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
kkunderwood
Join Date 10/2003
+10
Reply #39 July 21, 2018 5:21:06 PM
from WinCustomize ForumsWinCustomize Forums

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

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
AzDude
Join Date 11/2002
+555 sdemployee
Reply #40 July 21, 2018 5:29:01 PM
from Stardock ForumsStardock Forums

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

 

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
Uvah
Join Date 05/2006
+874
Reply #41 July 21, 2018 5:32:41 PM
from WinCustomize ForumsWinCustomize Forums

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

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
AzDude
Join Date 11/2002
+555 sdemployee
Reply #42 July 21, 2018 5:34:57 PM
from WinCustomize ForumsWinCustomize Forums

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.

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
Uvah
Join Date 05/2006
+874
Reply #43 July 21, 2018 5:35:53 PM
from WinCustomize ForumsWinCustomize Forums

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

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

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
AzDude
Join Date 11/2002
+555 sdemployee
Reply #44 July 21, 2018 7:44:03 PM
from WinCustomize ForumsWinCustomize Forums

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.

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
kkunderwood
Join Date 10/2003
+10
Reply #45 July 21, 2018 10:18:17 PM
from WinCustomize ForumsWinCustomize Forums

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.

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
gvse
Join Date 10/2007
0
Reply #46 July 22, 2018 5:51:27 AM
from Stardock ForumsStardock Forums

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)

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
basj
Join Date 03/2001
+1603 sdemployee
Reply #47 July 22, 2018 7:58:51 AM
from Stardock ForumsStardock Forums

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.

 

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
gvse
Join Date 10/2007
0
Reply #48 July 22, 2018 10:02:59 AM
from Stardock ForumsStardock Forums

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.

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
danamw@gmail.com
Join Date 02/2017
+1
Reply #49 August 25, 2018 3:07:25 PM
from Stardock ForumsStardock Forums

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.

Reason for Karma (Optional)
Successfully updated karma reason!
Nakor
masterbas
Join Date 09/2009
+1
Reply #50 August 28, 2018 12:31:40 AM
from Stardock ForumsStardock Forums

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

 

edit : still bit laggy on closing tho

Reason for Karma (Optional)
Successfully updated karma reason!
3 Pages1 2 3 
Stardock Forums v        Server Load Time:   Page Render Time: