Message boards :
Questions and problems :
Mac Interface issue
Message board moderation
Author | Message |
---|---|
Send message Joined: 23 Feb 08 Posts: 2465 |
If you attempt to quit BOINC from the icon in the bar, it puts up a modal dialog asking if you want to quit the science apps. Then immediately covers that dialog box with the application display. However the issue is that it is waiting for a click in the dialog box which is now hidden, freezing the interface without any obvious way to escape. |
Send message Joined: 2 Jan 14 Posts: 276 |
|
Send message Joined: 23 Feb 08 Posts: 2465 |
What version of BOINC and OS X? BOINC 7.2.42, Darwin 12.6.0 |
Send message Joined: 23 Feb 08 Posts: 2465 |
What version of BOINC and OS X? Edit, not that I'm back in front of the machine, make that BOINC 7.4.36. |
Send message Joined: 29 Aug 05 Posts: 15484 |
From Charlie: I tested this very thoroughly (including under Darwin 12.6.0) and could not reproduce the problem he reports. However, I did find a related bug. When we modified the task bar icon logic for the upgrade to wxWidgets 3.0 (BOINC 7.3.0), that introduced a bug which caused the Exit Confirmation Dialog to _not_ be shown at all (i.e., skipped) on the Mac when the user selects Quit from the menubar icon menu (taskbar menu), though it works correctly when Quit is selected from the Dock icon menu or from the regular menus. I wonder if he is misinterpreting the fact that this dialog is not shown at all so that he thinks the dialog is hidden behind another window. But when I select Quit from the menubar icon menu, BOINC exits immediately, so it is unclear what is causing the problem he is seeing. This bug (failure to exists through BOINC 7.6.2, but I checked in a change tonight to trunk and to the 7.6 branch so it will be fixed in 7.6.3. Cheers, --Charlie |
Send message Joined: 23 Feb 08 Posts: 2465 |
From Charlie: Just so we are sure, at the beginning BOINC was hidden, quit selected from DOCK (at bottom) it drew the exit confirmation and about 0.1 seconds later put the application in front, which was full screen. Have no issues when selecting quit from the BOINC menu (top left) or using key shortcut. Don't remember issues ever selecting it from the taskbar (at top right), that is actually the menubar per Mac documentation. Wondering if it is the same issue where on Charlie's system there wasn't a delay between the exit confirmation and it being covered, so he did not know it was hidden? In any case selecting finder as the front application brought the dialog box on top, as well as opening a new finder window. I haven't tried playing with BOINC at less than full screen for the application. Gary |
Send message Joined: 17 Jul 06 Posts: 287 |
Just so we are sure, at the beginning BOINC was hidden, quit selected from DOCK (at bottom) it drew the exit confirmation and about 0.1 seconds later put the application in front, which was full screen. What do you mean by which was full screen? How did you make BOINC appear full screen on Mountain Lion? In my testing, I arranged the main BOINC window to cover the same area as the exit confirmation dialog (though not the entire screen.) I tested it selecting Quit front the Dock both with BOINC hidden and shown, and both with and without the Event Log displayed. The Confirmation dialog appeared on top of the main window every time. In any case, BOINC 7.4.36 is long deprecated. Do you have the same problem with BOINC 7.4.42? Please also try BOINC 7.6.2 to see if the problem has been corrected for the next release. You can these here. Charlie Fenton BOINC / SETI@home Macintosh & Windows Programmer |
Send message Joined: 23 Feb 08 Posts: 2465 |
Just so we are sure, at the beginning BOINC was hidden, quit selected from DOCK (at bottom) it drew the exit confirmation and about 0.1 seconds later put the application in front, which was full screen. How full screen? Long long time ago I believe I hit the green plus button and then the red x button. Since that time on my system it has always opened full screen. I did try updating to 7.4.42 at one point. Doing so broke the VM with it giving me messages that it failed to start, so I had to roll back. On that for a second, anything I need to do to make it go forward clean, e.g. reset the projects using the VM? In playing with it again in the last few minutes it seems to be working correctly now with 7.4.36. So I'm willing to put it down to transient error or perhaps the exact mix of jobs running on my machine at the time (a race?). Thanks for looking into it. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.