Latest update to WB causes some applications and dialogs to lose their title bar

I have to use Task Manager to move or close these windows!

I am regretfully abandoning WindowBlinds. The latest update, installed November 7, 2016, caused some applications (such as VLC), and some modal dialogs, to lose their title bars, meaning there was no way to move the application or dialog, dismiss the dialog, or exit the application, except by finding its entry in Windows Task Manager and closing it from there. Also, the update caused WindowBlinds to disappear from the wretched Start menu. I think this is sloppy work, folks, and I do not have the patience to put up with it going forward.

30,521 views 27 replies
Reply #1 Top

I would recommend you contact support as that is not normal!

Are the titlebars missing all the time, or do they vanish after some time?  Also have you tried other themes?

Reply #2 Top

So Alt+Space doesn't bring up a dialogue box  that lets you "move" "minimize" "maximize" "size" "close"?

Reply #3 Top

Quoting Neil, reply 1

I would recommend you contact support as that is not normal!

Are the titlebars missing all the time, or do they vanish after some time?  Also have you tried other themes?
End of Neil's quote
Having this issue too with some apps, for instabce "Wise registry cleaner", and They are half showing on some but never functioning/responding .  :cylon:

Reply #4 Top
Quoting neone6, reply 3
Quoting Neil Banfield,

I would recommend you contact support as that is not normal!

Are the titlebars missing all the time, or do they vanish after some time?  Also have you tried other themes?

Having this issue too with some apps, for instabce "Wise registry cleaner", and They are never present.  :cylon:

End of neone6's quote

You should have reported it to us.

Having quickly looked at that app I think the issue is probably different to that reported by the thread creator however.  That app appears to have its own custom skinning engine providing titlebars and that's caused a problem.  We will ensure it is excluded in future updates.

Are there other apps showing the same problem?

Reply #5 Top

Thanx Neil, will check.  |-)

Edit: Only one so far.

By the way, BIG thanx 4 all the awesome work you're doing so we can keep up our end of the business ;)

Reply #6 Top

Quoting neone6, reply 5

Thanx Neil, will check.  |-)

Edit: Only one so far.

By the way, BIG thanx 4 all the awesome work you're doing so we can keep up our end of the business ;)
End of neone6's quote

Was this an issue in the previous versions of WindowBlinds too?

Reply #7 Top

Quoting Neil, reply 6

Was this an issue in the previous versions of WindowBlinds too?
End of Neil's quote
Yes.

Reply #8 Top

Title bars always missing on the same apps/dialogs, right from the get-go.

Reply #9 Top

Quoting cstallard222, reply 8

Title bars always missing on the same apps/dialogs, right from the get-go.
End of cstallard222's quote

Other than VLC could you mention some others so we can investigate to see if we can reproduce?

Also what skin are you using and which OS is this?

Reply #10 Top

This issue I encountered after the latest update. The screenshot I put up in another thread shows WB config open with no title bar etc. The skin I was using was Precision, one made for Win 7. Skins made for Win 10 however run without a hitch. I;m using Ice now and all my apps are skinned.

Reply #11 Top

Quoting Uvah, reply 10

This issue I encountered after the latest update. The screenshot I put up in another thread shows WB config open with no title bar etc. The skin I was using was Precision, one made for Win 7. Skins made for Win 10 however run without a hitch. I;m using Ice now and all my apps are skinned.
End of Uvah's quote

If it is happening with one skin it is probably a corrupted skin.  Go to the directory and delete *.WB64 and *.WB4 and try again.

Windows 7 designed skins are expected to work on Windows 10.  In fact there is basically no difference between those skins.

I imagine this is also different to the original thread issue which sounded selective in terms of which windows showed frames and which did not.  Your issue sounds like it would be all windows would it not?

Reply #12 Top

Not sure if this is the same thing, but on some  windowblind skins, the window is to big for the frame.

Reply #13 Top

Quoting cardinalsyn_25, reply 12

Not sure if this is the same thing, but on some  windowblind skins, the window is to big for the frame.
End of cardinalsyn_25's quote

Which skins and could you provide a screenshot of what you mean?

Reply #18 Top

Windows 10, and my short-term memory isn't helping me recall most of the dialogs. One was the Stickies management dialog. There were others. I would have opened a support ticket, but Stardock chose not to recognize my password, which did not give me a warm fuzzy feeling.

Reply #19 Top

I believe the skin was Cadera, and I won't be able to provide a screenshot until/unless I have time to try WB again. Not really willing...

Reply #20 Top

Quoting cardinalsyn_25, reply 17

Only a few skins are like this, the rest are good.
End of cardinalsyn_25's quote

Could you provide a list so we can try to reproduce please.

 

Also what is your display scaling setting set to?

Reply #21 Top

Display setting is 1920x1080

 

Corcyrah

Fearomone

Fearomone Invasion

Inkubus

There could be more, but this is a start

Reply #23 Top

The issue seems to have cleared itself up. I'm not able to reproduce the problem and all my skins are behaving themselves. Go figure.

Checked the directory and there is no ,WB4 or .WB64

Reply #24 Top

I updated Pale Moon to version 27 the other day, and now the title bar is not painted except when using default WB windows10 theme. Already posted at their bug section.

Reply #25 Top

Quoting gvse, reply 24

I updated Pale Moon to version 27 the other day, and now the title bar is not painted except when using default WB windows10 theme. Already posted at their bug section.
End of gvse's quote

Three options right now :

1) Switch over to Firefox which does skin properly

or

2) Rename Palemoon.exe to firefox.exe which will make WB think it is Firefox and enable compatibility for how it handles its titlebar.

or

3) Add an exclusion to make WindowBlinds not skin palemoon.exe

Please note that option 2 will result in some poorly painted titlebar text which is due to a Firefox bug fix which PaleMoon does not need.

I will make sure the next WB update considers PaleMoon to be Firefox complete with all Firefox's quirks other than the one causing bad titlebar text.