Re: [boinc_dev] Small tweak to next release would be, appreciated

[Robert Miles]

How reasonable would it be to put most of the display windows on the 
same screen as
before, but add a new item to at least one of the other screens?  The 
new item should

offer two choices :

1. Close the new item's window.

2. Move most of the display windows to this screen, then close the new 
item's window.


Robert Miles


Date: Thu, 2 Nov 2017 11:37:48 +0200
From: Vitalii Koshura 
To: Richard Haselgrove 
Cc: Chris Raisin ,   BOINC Developers Mailing
List 
Subject: Re: [boinc_dev] Small tweak to next release would be
appreciated

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 
:


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.

[snip]

Best regards,
Vitalii Koshura



___
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.

Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates

[Jacob Klein]

All right, thanks guys! I put on some hip-hop music to help me with my rapping 
skills. Testing now. Will reply back when it's done, hopefully tonight. "It's a 
dope app_info life that live I... going offline, test I will, see you, bye. 
Yoda I am not, but why am I still here? I swear I'll drop that exe, have no 
fear." Yeah, still working on it ..

From: David Anderson 
Sent: Saturday, November 4, 2017 8:06 PM
To: Juha Sointusalo; Jacob Klein
Cc: Boinc Projects; BOINC Developers Mailing List
Subject: Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates

I built new versions of vboxwrapper for Windows, which may work with VBox 5.2.0:
https://boinc.berkeley.edu/trac/wiki/VboxApps#Premadevboxwrapperexecutables
-- David

On 11/4/2017 10:49 AM, Juha Sointusalo wrote:
On 4 November 2017 at 16:27, Jacob Klein 
> wrote:
Rom has a checkin to fix the tlb to use the v5.2.0 release version instead of a 
pre-release version.
I think it needs merged.
It is located here:
https://github.com/BOINC/boinc/pull/2198

Could somebody please merge that, then convert that into a new VBoxWrapper that 
I can test?

Merged.

David, could you build a new version so that Jacob can start testing 5.2.0? I 
could send Jacob the one I compiled but I think a more official version would 
be appropriate.

-Juha


___
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.

Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates

[David Anderson]

I built new versions of vboxwrapper for Windows, which may work with VBox 5.2.0:
https://boinc.berkeley.edu/trac/wiki/VboxApps#Premadevboxwrapperexecutables
-- David

On 11/4/2017 10:49 AM, Juha Sointusalo wrote:
On 4 November 2017 at 16:27, Jacob Klein > wrote:


Rom has a checkin to fix the tlb to use the v5.2.0 release version instead 
of
a pre-release version.
I think it needs merged.
It is located here:
https://github.com/BOINC/boinc/pull/2198


Could somebody please merge that, then convert that into a new VBoxWrapper
that I can test?


Merged.

David, could you build a new version so that Jacob can start testing 5.2.0? I 
could send Jacob the one I compiled but I think a more official version would be 
appropriate.


-Juha



___
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.

Re: [boinc_dev] Small tweak to next release would be appreciated

[Richard Haselgrove]

I think it's better to think of Simple View and Advanced View as being two 
different programs, which don't inherit each others screen attributes. 

On Saturday, 4 November 2017, 19:32, Juha Sointusalo 
 wrote:
 

 On 4 November 2017 at 21:11, Chris Raisin  wrote:

> 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?
>

 Technicalities I think: the Simple View and Advanced View are different
windows and the Manager checks window's position when it's just about to
show it.

-Juha
___
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.

Re: [boinc_dev] Small tweak to next release would be appreciated

[Juha Sointusalo]

On 4 November 2017 at 21:11, Chris Raisin  wrote:

> 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?
>

 Technicalities I think: the Simple View and Advanced View are different
windows and the Manager checks window's position when it's just about to
show it.

-Juha
___
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.

Re: [boinc_dev] Small tweak to next release would be appreciated

[Chris Raisin]

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  
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:
"WindowMaximized"=dword:
"Width"=dword:05ba
"Height"=dword:040e
"XPos"=dword:01c6
"YPos"=dword:
"GUISelection"=dword:0001


On Thursday, 2 November 2017, 9:38, Vitalii Koshura 
 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 
:

> 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
> 

Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates

[Juha Sointusalo]

On 4 November 2017 at 16:27, Jacob Klein  wrote:

> Rom has a checkin to fix the tlb to use the v5.2.0 release version instead
> of a pre-release version.
> I think it needs merged.
> It is located here:
> https://github.com/BOINC/boinc/pull/2198
>
> Could somebody please merge that, then convert that into a new VBoxWrapper
> that I can test?
>

Merged.

David, could you build a new version so that Jacob can start testing 5.2.0?
I could send Jacob the one I compiled but I think a more official version
would be appropriate.

-Juha
___
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.

Re: [boinc_dev] Small tweak to next release would be appreciated

[Juha Sointusalo]

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:
> "WindowMaximized"=dword:
> "Width"=dword:05ba
> "Height"=dword:040e
> "XPos"=dword:01c6
> "YPos"=dword:
> "GUISelection"=dword:0001
>
> 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 :
> >
> > > 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 :
> > >
> > > 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 

Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates

[Jacob Klein]

Rom has a checkin to fix the tlb to use the v5.2.0 release version instead of a 
pre-release version.
I think it needs merged.
It is located here:
https://github.com/BOINC/boinc/pull/2198

Could somebody please merge that, then convert that into a new VBoxWrapper that 
I can test?

My goal is to get RNA World to use a wrapper that's compatible with VirtualBox 
5.2.x, which is important because of compatibility with Windows 10 while 
running the project's super-long-running monster tasks.

Let me know when I can test a new VBoxWrapper, please!

Thanks,
Jacob Klein

From: Jacob Klein
Sent: Sunday, October 29, 2017 6:27 PM
To: BOINC Alpha
Subject: Re: BOINC - October 2017 VirtualBox and VBoxWrapper updates

Bump.
Can someone please update the tlb with the v5.2.0 release version, and then 
compile a vboxwrapper that I can do some testing with?



From: Jacob Klein
Sent: Monday, October 23, 2017 3:01 PM
To: BOINC Alpha
Subject: Re: BOINC - October 2017 VirtualBox and VBoxWrapper updates

Can someone please update the tlb with the v5.2.0 release version, and then 
compile a vboxwrapper that I can do some testing with?

Please?

From: boinc_alpha  on behalf of Jacob 
Klein 
Sent: Wednesday, October 18, 2017 3:18 PM
To: BOINC Alpha
Subject: [boinc_alpha] BOINC - October 2017 VirtualBox and VBoxWrapper updates

Team,

Oracle recently announced the following releases:
- Oracle VirtualBox v5.2.0 Build 118431
- Oracle VirtualBox v5.1.30 Build 118389

VBoxWrapper code was recently changed to support v5.2.x, but the "vbox52.tlb" 
file was from v5.2.0 Beta 3. Now that the final version has been released, 
could we please get it updated with the "VirtualBox.tlb" file from the v5.2.0 
Final SDK, located here:
http://download.virtualbox.org/virtualbox/5.2.0/VirtualBoxSDK-5.2.0-118431.zip

Then, can we get an updated version of VBoxWrapper compiled, that uses it? I 
could try to test it when it is available, let me know. My main push for this 
is so that we can get a "5.2.x capable" version available for RNA World to 
quickly adopt, since some of their tasks take over 500 days to complete, and 
Windows 10 compatibility (with older VirtualBox versions) becomes an issue. Let 
me know when I can test it.

Regarding the version of VirtualBox that we include in the combined installers: 
It is my opinion that we should adopt the latest v5.1.x version, v5.1.30 as of 
right now. My reasoning is that v5.1.x is mature, and is only picking up 
bugfixes. Perhaps wait a month or two before adopting v5.2.x.

Thanks,
Jacob Klein
___
boinc_alpha mailing list
boinc_al...@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
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.

Re: [boinc_dev] BOINC Mac problem

[John Prewitt]

BOINC works on my MBP running Mac OS 10.13.2 Beta and BOINC 7.8.3.

John Prewitt

> On Nov 4, 2017, at 3:06 AM, Charlie Fenton  wrote:
> 
> Hi Aaron,
> 
> What version of BOINC are you running? BOINC 7.8.3 works fine for me under OS 
> 10.13.2. Did you try reinstalling BOINC after upgrading?
> 
> Cheers,
> --Charlie
> 
> On Nov 3, 2017, at 9:14 PM, David Anderson  wrote:
>>  Forwarded Message 
>> Subject: BOINC
>> Date:Fri, 3 Nov 2017 21:15:00 -0500
>> From:Aaron Shipley 
>> To:  da...@ssl.berkeley.edu
>> 
>> 
>> 
>> Dave,
>> 
>> I’ve updated my MacBook Pro to macOS 10.13.2 (it installed a beta release) 
>> and BOINC no longer works. I have no ability to open preferences or lots of 
>> other menu options that are grayed out.
>> 
>> I don’t know if this is a known issue, but maybe it will correct itself with 
>> a future update to macOS.
>> 
>> aaron.ship...@gmail.com 
>> 
>> Q: Why is this email five sentences or less?
>> A: http://five.sentenc.es
>> 
>> ___
>> 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.

Re: [boinc_dev] BOINC Mac problem

[Charlie Fenton]

Hi Aaron,

What version of BOINC are you running? BOINC 7.8.3 works fine for me under OS 
10.13.2. Did you try reinstalling BOINC after upgrading?

Cheers,
--Charlie

On Nov 3, 2017, at 9:14 PM, David Anderson  wrote:
>  Forwarded Message 
> Subject:  BOINC
> Date: Fri, 3 Nov 2017 21:15:00 -0500
> From: Aaron Shipley 
> To:   da...@ssl.berkeley.edu
> 
> 
> 
> Dave,
> 
> I’ve updated my MacBook Pro to macOS 10.13.2 (it installed a beta release) 
> and BOINC no longer works. I have no ability to open preferences or lots of 
> other menu options that are grayed out.
> 
> I don’t know if this is a known issue, but maybe it will correct itself with 
> a future update to macOS.
> 
> aaron.ship...@gmail.com 
> 
> Q: Why is this email five sentences or less?
> A: http://five.sentenc.es
> 
> ___
> 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.

Re: [boinc_dev] Fwd: BOINC Mac problem

[Richard Haselgrove]

Do we know if this person has updated to BOINC v7.8.3 ? 

On Saturday, 4 November 2017, 4:14, David Anderson  
wrote:
 

 FYI


 Forwarded Message 
Subject:     BOINC
Date:     Fri, 3 Nov 2017 21:15:00 -0500
From:     Aaron Shipley 
To:     da...@ssl.berkeley.edu



Dave,

I’ve updated my MacBook Pro to macOS 10.13.2 (it installed a beta release) and 
BOINC 
no longer works. I have no ability to open preferences or lots of other menu 
options 
that are grayed out.

I don’t know if this is a known issue, but maybe it will correct itself with a 
future update to macOS.

aaron.ship...@gmail.com 

Q: Why is this email five sentences or less?
A: http://five.sentenc.es

___
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.