Almost No Program Window Remembers It's Position In Windows 10 WindowBlinds

from Stardock Forums

Hi,

 

   The title pretty much explains my problem. Any suggestions? I had the same problem on the Windows 10 upgrade as well and am still having it on a "fresh install" option from the previous Windows 10 upgrade ..

 

The windows pretty much scoot over a few pixels every time I open them and I have them all placed where I like them.

No matter if it's an app or an installed program ..

If I unload WindowBlinds it puts the windows back where I had them unless I had adjusted them while it was loaded.

 

Googled it and no questions/bugs/answers about this, yet.

windowblinds
14,201 views 5 replies
Reply #1 from Stardock Forums Top

I can confirm this issue. Also many glitches with multiple display extended desktop.

Reply #2 from Stardock Forums Top

Quoting j800r1, reply 1

I can confirm this issue. Also many glitches with multiple display extended desktop.
End of j800r1's quote

Which version of WindowBlinds are you using?

Which apps are not repositioning correctly?

Also what issues are you having with multiple display extended desktop?

WindowBlinds 10.6 is about to leave beta so the sooner we know about problems the sooner we can investigate them.

Sins of a Solar Empire II
Reply #3 from Stardock Forums Top

I have 10.65 installed and I have this same issue in Windows 10.  I will snap my window to the side and it stays fine until I close and reopen it, then it is several pixels off when I reopen it.  If I select "Don not use per pixel frames even if the style supplies them" in settings, then the issue is gone, but the skin doesn't look nearly as good.  Qbittorrent doesn't get skinned correctly at all either.  This is with the themes Ice, Diamond, Acrylic 7,  and Eva that come with Windowblinds.

Reply #4 from Stardock Forums Top

I edited the skin "Ice" and removed the shadows from the per pixel frames and the windows properly position and qbittorrent gets skinned correctly.

Reply #5 from Stardock Forums Top

I figured I'd wait a few updates. Since WindowBlinds 10 was still in it's early stages back then. It seems fixed now.