Sticking, boinctasks js, and new v2 upcoming

[hucker]

I have grumbled in the past about using BOINC tasks to monitor 10 computers and every time one of those 10 computers is doing some scheduling the Boink client on that computer takes up an entire processor core for about 15 to 30 seconds which is extremely bad programming on the behalf of Poinke itself but the problem is when point tasks is waiting for that computer it won't allow me to interact with the interface whatsoever.

you have told me it may be better if I use the JavaScript version however I'm holding off on this because I've spotted you have version 2 of the non JavaScript programme in the works do you think this one might overcome the problem and when do you think it will be ready for beta test? I'm willing to try it as is if you want me to analyse it

[fred]

If the connection is stable you can go to the Setting->Expert tab and set the connection timeout to 2.
That said the OS may not always work as expected.

Most of the new work is on the JS version that is much easier to maintain.
There is no new release of BoincTasks in the pipeline, maybe some bug fixes.

[hucker]

So V2.00 beta TBA is just bug fixes?  I'll try js version sometime....

The problem is boinctasks not being usable because one of the computers isn't responding.  Boinc client is a buggy piece of crap and takes several seconds even on a fast machine to decide which project to contact next.  On an old machine it can be 30 seconds or more.  During this time the boinc client on that machine cannot be interfaced with by me, or by boinctasks.  If any of the computers are in the middle of this, I can't use boinctasks.  Boinctasks needs to display whatever computers it has information for and not make me wait.   Just show the last available data for every machine until you receive new data.