WindowFX 6.13 Beta Issue Thread

With the WindowFX 6.13 beta release today, we are creating this thread so that users can report any observed issues.  

Obtaining the beta:

Individual purchases (as well as Object Desktop Members) can also be obtained from your account page:

https://store.stardock.com/myaccount/products

Reporting an issue:

Please include the following for anything found:

  • Exact Windows version \ build (winver.exe)
  • Detailed steps to recreate the issue seen
  • Screenshots and videos are very helpful.  Videos can be uploaded to a cloud drive services (GoogleDrive, DropBox, OneDrive, YouTube) and link included in your post.  Images can be directly added.
  • If there are specific apps that Groupy does not work (well) with, please note what apps and their exact versions.  If any app is not common, a link to a trial version would be appreciated.

Thank you for your interest and any time you put into making WindowFX a better product.

52,279 views 29 replies
Reply #1 Top

WindowFX 6.13 Changelog

  • Adds in Windows 11 animations
Reply #2 Top

***Reserved***

Reply #3 Top

haha nice. I was literaly just talking about this

Reply #4 Top

So another issue I notice is when using the momentum dragging. Even with the "Keep entire window inside screen edges ..." option on it does not always work. When slamming to the left using the wfx config window it will indeed bounce however to the right it goes completely offscreen.

I'm running 3 monitors setup with a 48" 4k top monitor and 2 28" 1080's below (triangle pattern if you will). This occurs on the upper 48" but not the bottom satellites. I believe wfx is using the workspace which is of course the union of all 3 monitors (smallest rect that encompasses all 3 monitors). So the window is still within the workspace but you can't see it because it's on the top monitor. 

I confirmed this by using a window with a very large width. It leaves the right side of the top monitor but then bounces back when it hits the outer edge. It just so happens the size of the wfx config window is smaller than the extra right side space in my setup. 

Perhaps using the monitor rect instead of workspace rect could be an option?

Reply #5 Top

Quoting Narusegawa, reply 3

haha nice. I was literaly just talking about this

We talked about you in our meeting today actually  😁

Quoting Narusegawa, reply 4

So another issue I notice is when using the momentum dragging. Even with the "Keep entire window inside screen edges ..." option on it does not always work. When slamming to the left using the wfx config window it will indeed bounce however to the right it goes completely offscreen.

I'm running 3 monitors setup with a 48" 4k top monitor and 2 28" 1080's below (triangle pattern if you will). This occurs on the upper 48" but not the bottom satellites. I believe wfx is using the workspace which is of course the union of all 3 monitors (smallest rect that encompasses all 3 monitors). So the window is still within the workspace but you can't see it because it's on the top monitor. 

I confirmed this by using a window with a very large width. It leaves the right side of the top monitor but then bounces back when it hits the outer edge. It just so happens the size of the wfx config window is smaller than the extra right side space in my setup. 

Perhaps using the monitor rect instead of workspace rect could be an option?

Is it possible to post a video of the issue?

Sean Drohan
Stardock Product Lifecycle Manager

 

Reply #6 Top

Quoting sdRohan, reply 5


Quoting Narusegawa Naru,

haha nice. I was literaly just talking about this



We talked about you in our meeting today actually  😁


I'm almost afraid to ask lol. All good I hope.

 
Quoting sdRohan, reply 5
 
Quoting Narusegawa Naru,

So another issue I notice is when using the momentum dragging. Even with the "Keep entire window inside screen edges ..." option on it does not always work. When slamming to the left using the wfx config window it will indeed bounce however to the right it goes completely offscreen.

I'm running 3 monitors setup with a 48" 4k top monitor and 2 28" 1080's below (triangle pattern if you will). This occurs on the upper 48" but not the bottom satellites. I believe wfx is using the workspace which is of course the union of all 3 monitors (smallest rect that encompasses all 3 monitors). So the window is still within the workspace but you can't see it because it's on the top monitor. 

I confirmed this by using a window with a very large width. It leaves the right side of the top monitor but then bounces back when it hits the outer edge. It just so happens the size of the wfx config window is smaller than the extra right side space in my setup. 

Perhaps using the monitor rect instead of workspace rect could be an option?



Is it possible to post a video of the issue?


Sean Drohan
Stardock Product Lifecycle Manager

 

 

I'm not very good with making vids but I'll give it a go. There is also another issue involving the same feature with mixed DPI's I'll try to get a vid of that too.

Reply #7 Top

Lol clearly I fail to understand the quoting system. So here's a quick vid let me know if it helps or if I can do something else.

Also now you got me curious I don't think I've ever been the topic of a corp meeting before. 

Reply #8 Top

Here is another vid of an issue when using per monitor mixed mode. You can see that throwing the window from the upper 48" to the lower 28" the window flows down, Resizes to the smaller DPI, then is repositioned to be back on the upper 48", and finally continues it's animation. Depending on how hard you yeet it, it may continue to the lower monitor or simply run out of steam. When clicking it again after the animation it's correctly resized to fit the DPI of whatever monitor it ended up on but not until clicking. Even after the animation ends.

 

BTW:

In case it matters (and likely does) This is with 22H2.

Reply #9 Top

Also noticed that right clicking the tray icon opens the cfg window but only if its pinned. If the icon is in the tray overflow a right click does not work.

Reply #10 Top

Hello Naru,

Can't see the video, might need to set it to public for everyone to see it.

Thank you,

Basj,
Stardock Community Assistant

Reply #11 Top

oh crap. thanks basj. please try again i changed it. 

Reply #12 Top

Quoting Narusegawa, reply 11

oh crap. thanks basj. please try again i changed it. 

Thanks. Its showing now. :thumbsup:  

Basj,
Stardock Community Assistant

+1 Loading…
Reply #13 Top

Issue 3. This time with wobbly windows. Promise this is the last issue for the night (considering I've been awake for almost 90 hours lol).

Im using the stock Compiz style setting. You will notice that upon entering the size-move modal loop the window appears to jump some distance below the cursor. Mouse appears to be abought 50 px above the window caption (accounting for the 175% dpi on the top monitor).

Movement works fine (aside from above) until moving to a bottom monitor in which the window disappears. Would I be correct in assuming wFX is using a composited ghost that just isn't shown thereby hiding the actual window? 

On exit of the modal loop the actual window is shown in the correct position it seems only the display during the move loop is erroring.

If it matters I'm using an AMD RX5500 XT 8GB card with up to date drivers.

This issue was actually present in Windows 10 and I "think" W7 but I can't remember for sure.

Edit:

I noticed that this only seems to happen in the following windows

1. mIRC

2. TaskManager

The following don't do it.

1. VS

2. Edge

3. Firefox

Heres a link

Reply #14 Top

For some reason, this beta isn't showing for me in ODM.

Reply #15 Top

As far as I knew it isn't a part of OD. I had to purchase it separately. Or did you mean the downloads page which is where I Found it?

Reply #16 Top

Quoting RedneckDude, reply 14

For some reason, this beta isn't showing for me in ODM.
I never use the ODM, but the beta(s) should be available from your account page [Link]. Depending on when you subscribed or what period(s) you've had a subscription to OD, the apps included may vary a lot. I've been around a while so the list has grown quite long:

Reply #17 Top

Quoting JanOscar, reply 16


Quoting RedneckDude,

For some reason, this beta isn't showing for me in ODM.

I never use the ODM, but the beta(s) should be available from your account page [Link]. Depending on when you subscribed or what period(s) you've had a subscription to OD, the apps included may vary a lot. I've been around a while so the list has grown quite long:


Yours is there because you have been a client since shortly after the crust of the earth cooled 😉 (which we are very grateful for btw).

But yes, WinFX was removed from OD a couple of years ago now. 

Sean Drohan
Stardock Product Lifecycle Manager

+2 Loading…
Reply #18 Top

Quoting Narusegawa, reply 15

As far as I knew it isn't a part of OD.
Wow, I have had it for so long, I didn't realize it isn't part of ObjectDesktop.

Reply #19 Top

Quoting sdRohan, reply 17

Yours is there because you have been a client since shortly after the crust of the earth cooled 😉 (which we are very grateful for btw).
LOL, funny.  

Reply #20 Top

Upon release will my current key cover this or am I going to need to upgrade?

Reply #21 Top

Quoting Narusegawa, reply 20

Upon release will my current key cover this or am I going to need to upgrade?

I believe, if it is release under V6.xx than it is an update not an upgrade. So, it should work with your V6.XX key.

Thank you,

Basj,
Stardock Community Assistant

Reply #22 Top

Here's one on the Windows flip option. 

Notice when right clicking the max button you get the window menu first. A second attempt simply causes the window to disappear. It must then be terminated in task manager.

Reply #23 Top

Thanks Basj I guess I should have realized that but wasn't 100% what version it will be released as.

Reply #24 Top

I am stuck here:

No matter what I clock, nothing happens. Had to cancel via taskmanager and could normally install now. Perhaps just a glitch in the matrix. ;-)

Reply #25 Top

Quoting c242, reply 24

I am stuck here:

No matter what I clock, nothing happens. Had to cancel via taskmanager and could normally install now. Perhaps just a glitch in the matrix. ;)

What if you install from your account page:

https://store.stardock.com/myaccount/products

Sean Drohan
Stardock Product Lifecycle Manager