Sage 50 Pro Accounting Windows Randomly Maximizing

Win10 version 1909, Groupy v1.32, and Sage 50 Pro Accounting, release 2017.2.

Groupy works well with all my applications, except Sage.  After a short time working in Sage, opening and closing app windows and dialog boxes, Sage windows will briefly stop responding to mouse clicks (but not to window moves by dragging the title bar), then move some windows from one monitor to another (I have 3), and some, but not all, of the windows will maximize.  No other application is affected when this occurs.  After that happens control returns but I have to resize each affected window using the window restore button in the upper right and then reposition it.  This behaviour is always preceded by a couple of seconds of Sage not responding in any of its non-modal windows.

This happens regularly and frequently until I turn Groupy off on its application window.  Sage windows' size and location remain steady and respond as expected to mouse clicks.  I have tested this just through daily Sage use.  I didn't realize that Groupy was causing it until I turned it off in mid frustration ;-)

I have set Groupy to never automatically group Sage windows.  Sage is installed on a local drive but accesses NAS storage data (the same can be said of my Outlook 365 and Visual Studio 2019 installs which work flawlessly).

Is it just Sage?

8,233 views 4 replies
Reply #1 Top

Hello,
I have forwarded your questions/problems to the Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

Reply #2 Top

Any update to this problem?  A similar problem occurs with MS Visual Studio 2019 (I added my report in another thread).

Reply #3 Top

Just close the loop on this one, since Stardock staff don't seem interested, one of the updates in the last 18 months has solved the problem.  Neither Sage nor Visual Studio suffer any problems with Groupy now.

Reply #4 Top

Quoting ddminnl, reply 3

Just close the loop on this one, since Stardock staff don't seem interested, one of the updates in the last 18 months has solved the problem.  Neither Sage nor Visual Studio suffer any problems with Groupy now.
End of ddminnl's quote

Unfortunately the information may make it to development (hence the fix) but not where it came from so the thread may not get updated.

I am pleased the issue was resolved for you which is the important thing.