Page 1 of 1
Scheduler Validity Period

Posted:
01 Aug 2010 11:09
by siavoshkc
There was a problem:
You had set a task to be executed in 6:30 am, Shut Down PC for example on everyday. When you run Shareaza at 7 pm next day surprisingly PC counts down for Shutdown. This is because its passed 6:30 and download is for every day so shutdown task has to be executed.
The solution is to set a validity period for each task. For example when I set validity period for shut down task, say 5 minutes, shut down task is only valid until 6:35. After that it won't be executed for that day.
Versioning for XML export is also added.
Patch is update. Please commit ASAP.
Re: Scheduler Validity Period

Posted:
05 Aug 2010 15:09
by old_death
That's nice. Will that also make it possible to use the validity period to make Shareaza limit the used bandwidth, even if the PC is turned on after the rule execution started?
Re: Scheduler Validity Period

Posted:
09 Aug 2010 12:09
by siavoshkc
Re: Scheduler Validity Period

Posted:
11 Aug 2010 22:56
by ailurophobe
Not much else has been committed either so reasonable guess would be the devs are busy with RL.
Re: Scheduler Validity Period

Posted:
14 Aug 2010 15:03
by old_death
Yeah, there hasn't been posted code for almost two weeks before Ryo posted his code updates yesterday... I suppose he'll commit it once he had a look at this forum...
Re: Scheduler Validity Period

Posted:
15 Aug 2010 09:49
by siavoshkc
Delaying commit delays alpha tests. Also keeps my local repository in modified state which I hate.
Re: Scheduler Validity Period

Posted:
15 Aug 2010 18:58
by cyko_01
why was the entire designinfo section removed from shareaza.rc ? looks good other then that
Re: Scheduler Validity Period

Posted:
19 Aug 2010 13:06
by siavoshkc
Re: Scheduler Validity Period

Posted:
19 Aug 2010 23:41
by cyko_01
Re: Scheduler Validity Period

Posted:
25 Aug 2010 15:13
by old_death
Seems that Ryo reverted this commit because it broke compilation...
Re: Scheduler Validity Period

Posted:
26 Aug 2010 03:02
by cyko_01
Re: Scheduler Validity Period

Posted:
26 Aug 2010 21:12
by ailurophobe
You were not accused of anything that I noticed... But sure, now that ryo is around, he can do the commit once siavohkc figures out what went wrong. Something in Shareaza.rc maybe? That seems to be the only file your commit and the DC++ commit ryo did just before have in common and messing it up would "break compilation", I guess.
Re: Scheduler Validity Period

Posted:
27 Aug 2010 00:33
by kevogod
Re: Scheduler Validity Period

Posted:
01 Sep 2010 12:42
by siavoshkc
Of course I tested the code before placing it here it compiled and worked fine.
I updated to r8743 my local code and still everything is fine. Compiles and runs smoothly. Which means I have a running Shareaza with Validity Period while others don't.
Maybe the problem was with the package commited or Ryo changing icons.
Anyway here is another patch in r8743.
Re: Scheduler Validity Period

Posted:
02 Sep 2010 20:00
by raspopov
I hate diffs.

Please post complete files.
Re: Scheduler Validity Period

Posted:
05 Sep 2010 05:14
by siavoshkc
Here we go...
Re: Scheduler Validity Period

Posted:
05 Sep 2010 07:28
by raspopov
Committed but... Task dialog is very ugly. Can you follow MS GUI design guidelines?