Closed rerecrose closed 10 years ago
When this happens, what's the alien eye looks like? You can also enable 'verbose information in error console' (if not already ) and see in the error console for what happens after one run.
I also noticed one extremely case that when user never touch TB after it starts, the idle observer may not functional, hope this was not that.
And for the variable name, it's used like this: return this.start( self.isExceed ? autoArchivePref.options.start_exceed_delay : autoArchivePref.options.start_next_delay );
Archie's eye was closed
For instance, to see this by yourself.
-In the config dialog: set Time settings:->Start next run after 3600 secs (that makes an hour, Right :) ? -Then in Archie ^_^ contextual icon menu: Run Now (for several times just to make sure there is no partial work not done due to hitting some limit)
-After a final "Run Now" look at the status bar and see at what time is "Archie" pretending to be rescheduled again
for me... sometimes (I was not able to see why) it seems to use the limit_delay which I set to 60 seconds
Perhaps some flag gets signaled if some limit was hit and it does NOT respond well to further manual launching???
(This does not always happen, it appears to be some infrequent intermittent behaviour)
Can't re-produce, will checkin a potential fix soon, it's the only place that use limit_delay.
Thanks
please try https://github.com/wangvisual/autoarchive/blob/master/beta/awsomeAutoArchive-0.4-tb.xpi to test issue #10 and this one.
Closing as new version seem to solve the problem
Thanks a lot!
Testing with v 0.3
It seems that after a run it does NOT re-schedule after the programmed delay.
Perhaps there is an error and instead of the "variable" for "Start_Next_Run_After" the variable for "Start_Next_RunAfter(If_limit_reached)" ( I don't the exact names) is used by mistake
Could you please check it ?.
thanks