I would like for the BOINC's tooltip to fade away after moving the cursor.

You know, like the clock does. I dislike having to close out the tooltip every time I just want to do a quick check of how far along it is progressing.

Sekerob:


Correct.

I'm convinced that the multi-project DC's who run various sciences with diverse durations, for whatever reason, would benefit from separately tracking the various progress parms in the client_state.xml from which the client task scheduler computes the Time to Complete and the amount of work to cache. In WCG's case with currently 5 projects running, 5 different sets, thus ending volatility of durations of e.g. HPF2 to impact DDDT or DDDT impacting FA@H etc. The yoyo on DDDT is fun to watch how going from an 1 hour to 25 minutes to 3 hours as a slow Project job passes with hi resource demands.... the 'conservatives' algorithm reversing any adjusting done my a series of faster jobs. Nullifies any effect of setting the Additional Buffer aka Cache function and only invites to set it higher than need be, knocking on for those clients to have poor return times and making the rest in a quorum waiting for longer to see validation. I think overall it would help to reduce needs for storage capacity but mostly how much the scheduler daemon needs to keep track off.... reduced Result Status page counts per member, decreasing the amount of website hits another benefit... the knife cutting on both edges.

my 2 cents.

The reason I would like to control the length of time for snooze is that sometimes I have to snooze BOINC to get back enough memory to do some active work.

Sometimes that active work is only 10 minutes in duration but I commonly forget to unsnooze BOINC. Other times I am performing a long running winzip and would like to set the snooze for 2 hours.

This request is more of a convenience for me.

Automatic update feature would be nice, with an option to:
1.automatic download & manual install
2.automatic download & install
3.manual download & install

off course that feature would be commanded not by new version of the BOINC, but with the server prefered version, for example:
if the most current is 5.10.27, and the WCG runns with 5.10.22 (preffered), and another project (if you run on multiple servers) for example Rosseta@home runns on 5.10.17 -> then the computer will run the 5.10.17 version for all calcs!
(these numbers are for current version, and they are to piont out the example, not to show that what cannot be done with those versions)


GPU utilisation, will we see that?
the one that will use the DirectX or glide3D, so that it could be run on any graphic card and not only the newest...with an option which graphic card to use, 'cause some of us have more that one graphich card in system!