Multiple Monitors

I use 3 displays and love groups but it can be quirky with multiple monitors. One such issue is Outlook where I may open outlook on one monitor. Get an email and open it (I have groupy group all outlook for windows together because I hate having to search and close them all later) I then move the grouped outlook windows to a new monitor so I can refer the the just opened email while I type up something. When I finish and click back to the main outlook window, all the grouped application moves to another display where I originally opened outlook. If I click back on the email I opened the group of windows moves to the other display.

It can get very hard to keep up and work with it when I have a few windows going. I would think the grouped apps should update to the display of the grouped window.

if you get 3-4 more windows on different screens grouped it can go into lagging screen redraw loops for a bit (always seems to come out of it after 45seconds to 70seconds)

 

3,874 views 3 replies
Reply #1 Top

Hello,

Sorry to hear you are having issues. Could you post a video grab of this issue here, so that we can understand your problem more.

Thanks

Basj,

Stardock Community Assistant.

Reply #2 Top

Hello,

Sorry to hear you are having trouble.

When I finish and click back to the main outlook window, all the grouped application moves to another display where I originally opened outlook. If I click back on the email I opened the group of windows moves to the other display.
End of quote

This was resolved with Groupy 1.2.  Are you certain you are running the most current version (1.21)?

Sean Drohan
Stardock Support Manager

Reply #3 Top

I am and when I went through all my tests, it initially switched screens on opening a new email message (outlook was on display 1, open new email message moved to display 3) but since going through it all one time then starting over it is not happening at the moment. I will continue to test to see if I can find any criteria that reproduces it reliably but it is not easily reproducible now. if at all. Maybe initially with 1.21 it did it because window positions were stored/cached somewhere and when I ran thorugh my tests, it updated the stored/cached window positions to the correct values.

I will let you know if I see anything else with it but so far so good with 1.21