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&utm_
> source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
> > www.avast.com
> > <https://www.avast.com/sig-email?utm_medium=email&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.
