Groupy - 1.39 Beta Issue Report Thread

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

Obtaining the beta:

Object Desktop members can get the beta from within Object Desktop Manager with 'show beta downloads' enabled:

f

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

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

For guest check-out purchase (no account), from this link:

http://www.stardock.com/support/productkeyretrieval

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 links 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 Groupy a better product.

Sean Drohan
Stardock Support Manager

8,638 views 5 replies
Reply #1 Top

Changelog for 1.39

  • Fixed an issue where the min, max, close buttons could be clipped under certain conditions
  • To improve the success rate of adding an app to a group with delayed grouping enabled, to make it more obvious that an app will be grouped when moved to an area, we expanded the target zone to include the tabs when they are placed above the titlebar.
Reply #2 Top

With the release of Groupy 1.40, we are closing this thread.

Thanks for the time to test and feedback.

Sean Drohan
Stardock Support Manager

Reply #3 Top

Win10 v1909 b18363.997

See if this happens on a current version of Excel. Mine is ancient (Excel 2003) and I couldn't possibly expect it to be addressed. It's a little obscure, and if it happens on more current versions it could be more relevant, or perhaps provide insight to some "Groupy causes high CPU usage" problem.

To test, have Groupy turned on and Excel opened with only one file open. Hide the file/workbook and see if each the Excel and Explorer processes throttle. (Command to hide an open workbook on my ancient Excel is Window/Hide, hopefully it's something similar on a current version.)

Happens while Groupy is merely turned "On", doesn't need to have anything grouped. If Excel is open specifically with only a hidden window (hidden file) open and with no visible windows open, cpu usage for Excel and Explorer will each throttle. Unhiding the hidden file, or opening another file. or creating a new file, or closing Excel, or turning Groupy "Off" will stop the throttling. (If you turn Groupy back "On" while Excel remains in the same state, the throttling will start again.)

An example of where this would tend come into play is a worksheet of macros to be used across multiple Excel files, saved as "Hidden" both to protect it and because you don't really want it in the way.

I thought I'd pass it along in case it's useful. Thanks.

Reply #4 Top

Quoting DaveRI, reply 3

Win10 v1909 b18363.997

See if this happens on a current version of Excel. Mine is ancient (Excel 2003) and I couldn't possibly expect it to be addressed. It's a little obscure, and if it happens on more current versions it could be more relevant, or perhaps provide insight to some "Groupy causes high CPU usage" problem.

To test, have Groupy turned on and Excel opened with only one file open. Hide the file/workbook and see if each the Excel and Explorer processes throttle. (Command to hide an open workbook on my ancient Excel is Window/Hide, hopefully it's something similar on a current version.)

Happens while Groupy is merely turned "On", doesn't need to have anything grouped. If Excel is open specifically with only a hidden window (hidden file) open and with no visible windows open, cpu usage for Excel and Explorer will each throttle. Unhiding the hidden file, or opening another file. or creating a new file, or closing Excel, or turning Groupy "Off" will stop the throttling. (If you turn Groupy back "On" while Excel remains in the same state, the throttling will start again.)

An example of where this would tend come into play is a worksheet of macros to be used across multiple Excel files, saved as "Hidden" both to protect it and because you don't really want it in the way.

I thought I'd pass it along in case it's useful. Thanks.
End of DaveRI's quote

Thanks for the report.

I was able to reproduce this.  It is Excel not handling hidden windows well, but we have worked around it for 1.4.

Reply #5 Top

I'm glad that was useful.  I kept thinking "But it's Excel 2003."