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.
Ghosters
Ghosters
Join Date 05/2010
0

DisplayFusion compatiblity, Min/Max/Close = Restore

January 27, 2019 1:01:50 AM from Stardock ForumsStardock Forums

Win10 Pro 64, WB 10.73

When WB and DisplayFusion are running at the same time, the title bar buttons fail.

The min/max/close all do the same thing, max/restore.

Affects explorer, Firefox, Chrome, WB windows, DF windows...

Tried with various custom and included themes.

Default theme works, I think this is nearly equal to unloading WB?

I don't see any settings that might resolve this in either app.

Also, I ran across this https://www.stardock.com/products/windowblinds/docs/basic.asp ... where is this settings page?  Is it for real?

 

 

 

windowblinds
Search this post
Advanced Search
Subscription Options
Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
basj
Join Date 03/2001
+1603 sdemployee
Reply #1 January 27, 2019 1:20:49 AM
from Stardock ForumsStardock Forums

Hello,

Need more information.

1) Windows 10 version number. Please use winver.exe

2) DisplayFusion version.

3) Is the problem there is you disable displayFusion?

4) Is the problem happened on all style that come with WB?

5) Can you try the purge and reinstall steps and see if the problem goes away after reboot. : https://forums.stardock.com/486023/windowblinds-support-faq#reinstalling

Make sure to re-download the latest installer from your account. https://store.stardock.com/myaccount

Install that version, reboot and retest.

report back here.


Also, I ran across this https://www.stardock.com/products/windowblinds/docs/basic.asp ... where is this settings page? Is it for real?

I believe those a taken from older version of WB, Windows XP, and on longer available in current version.

 

Thank you,

 

Basj,

Stardock Community Assistant

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
Victechnical
Join Date 07/2014
+48
Reply #2 January 27, 2019 9:25:12 AM
from WinCustomize ForumsWinCustomize Forums

Quoting ,
quoting post

Win10 Pro 64, WB 10.73

When WB and DisplayFusion are running at the same time, the title bar buttons fail.

I've been using DisplayFusion together with WindowBlinds for a long time without any problems.  Currently I have Windows 10 build 1803, DisplayFusion 9.5 beta 1, and WindowBlinds 10.  By chance are you running an Insider build of Windows?

+1
Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
Ghosters
Join Date 05/2010
0
Reply #3 January 27, 2019 6:15:14 PM
from Stardock ForumsStardock Forums

I'm on 1709,  DF 9.5 b1, 10.73

Not insider.

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
basj
Join Date 03/2001
+1603 sdemployee
Reply #4 January 27, 2019 8:24:27 PM
from Stardock ForumsStardock Forums

Quoting basj,
reply 1

3) Is the problem there if you disable displayFusion?

4) Is the problem happened on all style that come with WB?

5) Can you try the purge and reinstall steps and see if the problem goes away after reboot. : https://forums.stardock.com/486023/windowblinds-support-faq#reinstalling

Make sure to re-download the latest installer from your account. https://store.stardock.com/myaccount

Install that version, reboot and retest.

report back here.

Answer for those?

Thank you,

 

Basj,

Stardock Community Assistant

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
RedneckDude
Join Date 04/2009
+2210
Reply #5 January 27, 2019 9:18:19 PM
from WinCustomize ForumsWinCustomize Forums

1709 is a bit old.

 

I've been using DisplayFusion together with WindowBlinds for a long time without any problems.  Currently I have Windows 10 build 1809, DisplayFusion 9.5 beta 1, and WindowBlinds 10.74. 

+1
Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
Ghosters
Join Date 05/2010
0
Reply #6 January 28, 2019 9:53:38 AM
from Stardock ForumsStardock Forums

Sorry, I tried with DF and WB one at a time, the issue requires both at the same time.

I tried built in profiles and custom, the issue does not seem to be specific to profiles.

Reinstall is a really good idea.

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
RedneckDude
Join Date 04/2009
+2210
Reply #7 January 28, 2019 10:18:26 AM
from WinCustomize ForumsWinCustomize Forums

Ghosters, are you using the DisplayFusion titlebar button?

I will enable it here and see if I can recreate your issue.

 

EDIT: Nope, can't make it happen here.

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
Ghosters
Join Date 05/2010
0
Reply #8 January 30, 2019 10:21:33 PM
from Stardock ForumsStardock Forums

I've removed WB and DF, choosing complete removal option.  After install, the problem remains the same.  With either app exited, titlebars are fine. 

Buttons work when:

  • WB and DF loaded with defaults (fresh install)
  • Fresh install and some built-in titlebar buttons enabled.
  • Added custom button using 13x13 icon (defaults are 11)
  • Added custom button using 22x22 icon.
  • Adjusted window border size.

Buttons failed on restore profile.  There's plenty more config to do, by restoring one thing at a time I may be able to determine the issue.  I'm guessing it was something corrupt / outdated setting left behind causing issues.

 

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
basj
Join Date 03/2001
+1603 sdemployee
Reply #9 January 30, 2019 10:40:35 PM
from Stardock ForumsStardock Forums

Quoting Ghosters,
reply 8

Added custom button using 13x13 icon (defaults are 11)
Added custom button using 22x22 icon.
Adjusted window border size.

Would like to know how you are doing these and if it using WB with Skinstudios? And you mentioned before "Profiles" what was it referring to?

Thank you,

 

Basj,

Stardock Community Assistant

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
Ghosters
Join Date 05/2010
0
Reply #10 January 30, 2019 10:45:07 PM
from Stardock ForumsStardock Forums

Update: DF padding + WB loaded = fail.

Tried with and without splits.  Any padding set in "splits and padding" breaks the titlebar buttons.

Setting the padding to 0 restores functionality.

 

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
Ghosters
Join Date 05/2010
0
Reply #11 January 30, 2019 10:51:54 PM
from Stardock ForumsStardock Forums

The custom buttons are part of DF.  I've installed skin studio and looked at it but have not saved (on this OS install).

 

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
RedneckDude
Join Date 04/2009
+2210
Reply #12 January 30, 2019 11:42:40 PM
from WinCustomize ForumsWinCustomize Forums

Quoting basj,
reply 9

And you mentioned before "Profiles" what was it referring to?
Jazlan, profiles are a set of settings saved as a profile in DF.

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
basj
Join Date 03/2001
+1603 sdemployee
Reply #13 January 31, 2019 12:06:23 AM
from Stardock ForumsStardock Forums

Quoting RedneckDude,
reply 12

Jazlan, profiles are a set of settings saved as a profile in DF.

Ah okay, got it. Thanks.

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
Ghosters
Join Date 05/2010
0
Reply #14 January 31, 2019 2:22:58 AM
from Stardock ForumsStardock Forums

Thanks, that's what I was referring to. 

DF profiles are for monitor configuration including splits, icons, screen saver, taskbar, and audio devices.

The issue is not simply padding.  

Saving DF settings can temporarily get it working.  After closing a window or 2... or3... it wont close anymore.  This sounds odd but there's a similar issue with one of the user scripts triggering from the title bar only the first time, requiring saving settings to trigger it again.  With the windows closing issue, mostly it lets me close notepad one time, but sometimes I get 2 or 3 closed.  Once it fails, it does not seem to recover itself.  I'm pretty sure that when the second notepad fails,  sometimes a chrome window might work once, but sometimes the max'd window seems to pop under, so when testing with more than one open, you have to watch the # open in the taskbar.

One gadget or another is broke now days.  It should not be so hard.  I may or may not look into this any further.  But chances are it is a DF, not a WB issue.

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
BuckoA512
Join Date 02/2017
0
Reply #15 August 16, 2019 5:59:15 PM
from Stardock ForumsStardock Forums

Old thread but having the same issue here, many of my apps won't minimise when DF and WB are running, its weird, on some apps clicking minimise is like clicking restore. Others (e.g Thunderbird) just don't do anything when I click minimise.

Windows 10 Pro 1903 build 18362.295

DisplayFusion Pro 9.5

WindowBlinds 10.82 (057 - Windows 10 Edition) - 64 bit OS

Window titlebar blur features are enabled on this operating system

        Wblind.dll                2019/06/25 20:37:48

        Wblind64.dll              2019/06/25 20:37:49

        Wbsrv.dll                2019/05/04 05:29:46

        WB10Config.exe            2019/06/25 20:37:54

        Wbload.dll                2019/05/08 21:13:37

        Screen10.exe              2019/05/04 05:29:17

 

I have my ultrawide split into 3 monitors, no padding but 2 splits.

Guess it's back to no Windowblinds... again

Reason for Karma (Optional)
Successfully updated karma reason!
Ghosters
BuckoA512
Join Date 02/2017
0
Reply #16 March 16, 2024 6:21:30 AM
from Stardock ForumsStardock Forums

Tried this again in 2024 and, well it seems better, but regrettably it still affects some apps.. shame, seeing Windows 11 with that awesome Dragon skin was very nostalgic but won't be buying once my 30 days is up because of this.

Real shame this can't be fixed I guess neither Stardock or Binary Fortress is willing to take the initiative.

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