Thanks for your contribution, Juha.
One further “snag” has crept in to the situation. I normally have the BOINC Manager running in “Advanced” Mode displaying the “Tasks” Panel, extended to the full height of the screen (and using 50% of the width), enough to see about 7 columns of data). I notice that when it IS displaying on the second screen, and I click on “View” in the menu to change the view to “Simple” view (or press “Ctrl” + “Shift” + “V”), the BOINC Manager panel switches back to the main screen (I assume that to be the default position). Switching to any other View is OK, but switching to “Simple” reverts back to the Main screen. Surely this is not a normal procedure in software, since any switch of views should always simply change only the view, not the position of the views . If not having the “Last Known Position” reinstated on start-up be thought a desirable implementation then can the anomaly of the “Simple” Mode switch sending the display to the Main screen instead of the current used screen be rectified? (By the way, if I change to “Simple View”, move the panel to the second screen, then switch to “Advanced View” it, also, sends the panel back to the Main Screen). All other switches of view keep the BOINC Manager on the screen currently in use, only switching to either “Simple View” or “Advanced View” sends the Manager careering back to the Main Screen. If this switch of views does that, why don’t all changes of views (such as changing to Statistics or back to Tasks) also do this? (I am not advocating that they all do, I would prefer the Manager to always stay on the screen on which it has been shifted (via a Click and Drag). Again, I think reverting the BOINC Manager’s default initial position to the “Main Screen” should be handled via a selection on the context menu , perhaps just above the current “Snooze” item). At least the BOINC Manager panel is then retrievable should the second screen be “out of action”. With this in place, I would think it safe to allow an restoration of “Last Known Position on closure” to be reinstated on start-up. More food for thought. J Cheers Chris From: Juha Sointusalo [mailto:juha.sointus...@gmail.com] Sent: Sunday, 5 November 2017 3:23 AM To: Richard Haselgrove Cc: Vitalii Koshura; BOINC Developers Mailing List; Chris Raisin Subject: Re: [boinc_dev] Small tweak to next release would be appreciated I don't think that having a setting for everything makes good software. It tends to be an awful experience to try to configure a software that has a hundred different settings. I would prefer a software that automatically does the right thing. Since the Manager already saves the window size and position, using the same display as the previously would, in my opinion, be the right thing to do. I think the Manager already has code that checks that the window titlebar is at least partially visible on primary display so all that would need to be done is change that check to make sure the titlebar is visible on some available display. Dialogs would need some additional care. At least some dialogs have their position (and therefore display) saved, but since they are modal dialogs I think they should open on the same display as the Manager main window. Event Log would be ok to open on the same display as previously. I don't think a broken backlight is a problem. If a monitor doesn't work you power it off or disconnect and therefore it is not available. If others firmly believe that it could be a problem I would suggest a "safe mode" that starts the Manager with default everything. -Juha On 2 November 2017 at 11:47, Richard Haselgrove <r.haselgr...@btopenworld.com> wrote: Thanks Vitali - that might do it. Although it isn't clear from the way that Chris worded the original request, BOINC does already remember the position of the Manager window between sessions: all that would be needed is to provide controls to over-rule the 'automatic re-home to display 1 at startup' code. Window location is stored in registry keys like [HKEY_CURRENT_USER\Software\Space Sciences Laboratory, U.C. Berkeley\BOINC Manager] "WindowIconized"=dword:00000000 "WindowMaximized"=dword:00000000 "Width"=dword:000005ba "Height"=dword:0000040e "XPos"=dword:000001c6 "YPos"=dword:00000000 "GUISelection"=dword:00000001 On Thursday, 2 November 2017, 9:38, Vitalii Koshura <lestat.de.lion...@gmail.com> wrote: Hello Richard, Thank you for you comments. In this case, I guess, we can make this configurable and let user decide whether he or she wants to keep BOINC window position or to see it always of the first display. Thanks Best regards, Vitalii Koshura 2017-11-02 11:30 GMT+02:00 Richard Haselgrove <r.haselgr...@btopenworld.com> : > I think we should be a little cautious about changing this: I think the > original decision to make all windows appear first on display 1 may have > been deliberate, and done for a purpose. Check the code for comments first. > > I use dual displays as well (1920x1200 and 1600x1200): I also have > multiple computers set up to use both those displays, via two separate KVM > switches. It gets quite complicated, especially because the machines have > three GPUs each, one an intel running headless. It can get confusing. > > The problem is, from experience: if a hardware display becomes unavailable > for any reason, but an application is set to start up on it, it can be > extremely difficult to restore the application to the visible primary > monitor. Software which is designed to 'always start on display 1', like > BOINC, is intended to be easily recoverable during hardware failure or > configuration changes. Remember that in some failure modes (e.g. backlight > failure), the monitor firmware can report 'all is well and usable' to > Windows during hardware detection at startup. > > > On Wednesday, 1 November 2017, 23:39, Vitalii Koshura < > lestat.de.lion...@gmail.com> wrote: > > > Hello Chris, > > Thank you. > I'll try to reproduce and fix it. > > Best regards, > Vitalii Koshura > > 2017-11-01 23:56 GMT+02:00 Chris Raisin <crai...@optusnet.com.au>: > > > Hi Vitalii, > > > > I run under Windows 10 (Latest public release) > > > > > > > > Cheers > > > > Chris > > > > > > > > *From:* Vitalii Koshura [mailto:lestat.de.lion...@gmail.com] > > *Sent:* Thursday, 2 November 2017 8:36 AM > > *To:* Chris Raisin > > *Cc:* BOINC Developers Mailing List > > *Subject:* Re: [boinc_dev] Small tweak to next release would be > > > appreciated > > > > > > > > Hello Chris, > > > > > > > > Just wondering which OS do you use to run BOINC? > > > > > > > > Thanks > > > > > > Best regards, > > > > Vitalii Koshura > > > > > > > > 2017-11-01 23:05 GMT+02:00 Chris Raisin <crai...@optusnet.com.au>: > > > > I have been a user of BOINC Manager for many years, but one thing > > continually "bugs" me. > > > > > > > > I run a system on which I have multiple screens, and I keep BOINC on > > screen > > 2 > > > > (away from my general "Work Area" on Screen 1). > > > > > > > > Every time I start up my system (albeit not often since it is normally > > running 24 hours per day) > > I have to manually move the BOINC screen from screen 1 to screen 2. > > > > (Screen 2 is really an extension of screen 1 since moving things to the > far > > left of screen 1 moves > > them on to Screen 2.) > > > > > > > > It would be great if BOINC could have a setting stored in the registry > that > > stores the screen > > location of the BOINC Manager every time it is moved. Upon start-up of > > BOINC, it could then read > > in the last stored location and move to that location initially. > > > > > > > > Just an idea. J > > > > > > > > Cheers to all > > > > > > > > Chris Raisin > > > > Australia > > > > > > > > > > > > > > > > > > --- > > This email has been checked for viruses by Avast antivirus software. > > https://www.avast.com/antivirus > > _______________________________________________ > > boinc_dev mailing list > > boinc_dev@ssl.berkeley.edu > > https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > > To unsubscribe, visit the above URL and > > (near bottom of page) enter your email address. > > > > > > > > > > <https://www.avast.com/sig-email?utm_medium=email > > <https://www.avast.com/sig-email?utm_medium=email&utm_> &utm_ > source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. > > www.avast.com > > <https://www.avast.com/sig-email?utm_medium=email > > <https://www.avast.com/sig-email?utm_medium=email&utm_> &utm_ > source=link&utm_campaign=sig-email&utm_content=emailclient> > > <#m_4063138380773232668_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > > _______________________________________________ > boinc_dev mailing list > boinc_dev@ssl.berkeley.edu > https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > > > _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
