Bugzilla – Bug 53
Issues if Audacity is quit on the second monitor
Last modified: 2018-08-20 11:51:22 UTC
* GA: Audacity does not come up on top after launch, requiring right-click > "Maximize" or "Restore" over Taskbar icon, ALT - tab or resetting .cfg (the latter always works). Some users believe Audacity has "stopped working". One user claimed these were the .cfg settings before resetting them: [Window] X=-4 Y=-4 Width=1288 Height=778 Maximized=1 * GA: Fix committed for case where relaunching executable when it was already open was causing the second project window to be hidden, then the x,y position would be saved in .cfg as off-screen. Not known if this cures the many cases reported, but GA has pushed the Nightly to a sample of users who complained about the problem. * GA: 05Dec 09 - one user report of a similar problem in 1.3.10 being looked into.
User who complained in 1.3.10 never responded. Maybe they were not actually using 1.3.10, but no further reports of this on Windows have been made. There has been a report April 2010 on OS X 10.6 of Audacity 1.3.10/11/12 not appearing when quit on a second monitor and restarted with the second unavailable: > I´ve been using Audacity on my MacBookPro with an additional external >(bigger) monitor, moved the window there for easier work and later on > quit Audacity. Then I happened to be on a different place, tried to > open Audacity and the window didn´t show, in fact it was placed on > the - now not existent - external monitor and I had to go through a > lot of tricks to make the window show again on the MacBook. Even > using another external monitor didn´t work in the beginning, only > by zooming out I was able to grab the menubar and pull the window > to the MBP Monitor. Koz tried to replicate the problem in 1.3.11 without success.No further input from user yet.
I think it is time to close this "fixed".
(In reply to comment #2) > I think it is time to close this "fixed". Has anything been fixed in the code in the interim? Clearly that user could repro it. Of course we have no idea of any monitor tweaks or monitor manager programs he may have. Also I found these three reports which occurred since the last report above (last in Dec 2010).The issue here seems to be that Audacity does not reappear properly on the second (available) monitor when it is closed on that monitor. They all seem to be 10.5.8 PPC machines. * Mac 10.5.8 G5 PPC , 1.3.12 (2 reports) * Mac 10.5.8 G4 PPC, 1.3.12 Here is the most detailed of the three reports. > I notice a display issue when using a second display: When I quit > Audacity with a window positioned on the second display, then next time > I open Audacity, the window is there as a white rectangle but not > accessible by clicking. I can use Audacity with menu commands and keys, > but not by using the GUI. The only way to get working again, apparently, > is to synchronize the displays from the Monitors Prefpane. > F11 helps (wasn't aware of this possibility), but recreating the > config file had no effect. The bug was not apparent 2 months ago, so I > suspect it's got to do with a recent MacOS security update. I am not currently in touch with any of these people, though I don't quite see the relevance of the security update. I don't know if Bill can test on a second monitor but I have added him to the Cc's. Have you any views on this, Ed? I certainly think the bug should remain open for tracking purposes given the above, but I've changed the bug title to "Issues if Audacity is quit on the second monitor".
(In reply to comment #3) > --- Comment #3 from Gale Andrews <gale@audacityteam.org> 2011-04-06 16:50:48 BST > --- (In reply to comment #2) > > I think it is time to close this "fixed". > > Has anything been fixed in the code in the interim? Nothing in Audacity has changed AFAIK since my committed fix in early 1.3.10 which should have fixed the original Mac bug report. > Also I found these three reports which occurred since the last report above (last in Dec > 2010).The issue here seems to be that Audacity does not reappear properly on the second > (available) monitor when it is closed on that monitor. This may be related to a known wxWidgets Mac issue for which a fix was made in the last few days. I do not know if the fix will filter down to 2.8.12. I would like to see the text of the other two reports entered here as well.
> This may be related to a known wxWidgets Mac issue for which a fix was made in > the last few days. I do not know if the fix will filter down to 2.8.12. Can you post a link/details? > I would like to see the text of the other two reports entered here as well. I don't think I retained the exact text, Ed, because it added nothing useful, and one of them was in the manner "crap software, going to GarageBand". It would have been something like "doesn't work" or "can't be seen" if you quit on the second monitor and re-launch.
(In reply to comment #3) > I don't know if Bill can test on a second > monitor but I have added him to the Cc's. My G5 supports a second monitor, so if you think it is important I could try to borrow one for a few hours.
(In reply to comment #5) from the wxWidgets dev mail list: [wx-dev] CenterOnScreen() function doesn't work well when changing resolutions. Acts erratically. Has anyone seen this behavior? Basically, I have a generic frame that has the Show() function overloaded. In that function I do CenterOnScreen(wxBOTH). This works well until my program is running and I change the primary monitor resolution. Then it will be off center. I am using a 3 headed system so maybe the code that handles figuring out the screen dimension of the primary screen is wrong. Actually I know it returns erroneously cause I traced it. The offending code is: int nDisplay = wxDisplay::GetFromWindow(GetParent() ? GetParent() : this); dpy(nDisplay == wxNOT_FOUND ? 0 : nDisplay); const wxRect rectDisplay(dpy.GetClientArea()); The rectDisplay size is incorrect. Anyways, I'll do the centering manually but has anyone seen this bug? Should note that my frame has a NULL parent if that matters. Rensy and Vadim Zeitlin <vadim@wxwidgets.org> replied: This should be fixed in recent svn. Before, the display geometry was cached and not updated when it changed. Regards, VZ ---------------------------- The important point being "the display geometry was cached and not updated when it changed". I cannot locate the thread discussing the fix right now but I think it was Mac-specific.
(In reply to comment #6) When practical, please borrow a monitor and give it a try. Remember to test with the secondary monitor on right, left, top and bottom (if Mac allows that). I think if this changes from moonphase to repeatable it should also bump from P4 to P3. The real problem is that there is no one to work on these less critical Mac items.
Lobbying to close this because we do have a new wxWidgets which should have any fixes to wxWidgets mentioned in the 2011 comment #7. We also have P3 Bug 1314 which is 'an issue' around quitting on the second monitor. That bug's existence indicates there have been significant changes in how we open windows on a second monitor since this bug was filed. The changes may still be wrong, per Bug 1314, but those changes probably render the buggy behaviour described here no longer relevant. I think the designation 'moonphase' may be incorrect and preventing us from progressing the status of this bug. The real issue is shortage of dual monitor macs in test/development. The moonphase designation could mean we keep a no longer valid bug open forever. Better to close it, and then if it occurs again add clearer information into Bug 1314 or create a new bug, depending on whether it is the same bug or a different one.
Gale wrote: > Also I found these three reports which occurred since the last report above > (last in Dec 2010).The issue here seems to be that Audacity does not reappear > properly on the second (available) monitor when it is closed on that monitor. > They all seem to be 10.5.8 PPC machines. We no longer support 10.5, but this is not an issue on 10.6.8. Gale wrote: > There has been a report April 2010 on OS X 10.6 of Audacity 1.3.10/11/12 not > appearing when quit on a second monitor and restarted with the second > unavailable: Tested this on 10.6.8 and 10.7.3 - no longer an issue. Audacity reappears centred on the first monitor. Ed wrote: > CenterOnScreen() function doesn't work well when changing resolution Tested on macOS 10.7.3, the behaviour doesn't seem significantly worse than with Apple apps, and is often improved by restarting Audacity with the new resolution in place, or is correctable by deleting audacity.cfg (Audacity is then centred again). Probably just about below the threshold of tracking (P6). So the sum of all that is to close this as FIXED.
