On Wednesday, July 29, 2020 at 8:50:33 AM UTC-7, Mat wrote:
>
> Eric Shulman wrote:
>>
>> uh oh.  This suggests something bad about how my $action-timeout code 
>> works.  Since the timeout widget re-invokes itself each second, I think 
>> it's leaving behind the previous "timed out" widget object, resulting in a 
>> slow accumulation of junk on the call stack.  This is *very* bad.  I will 
>> have to think about ways to re-write the underlying JS to not do this.  
>>  This likely also affects the basic "timer" functionality (if the timer 
>> runs too long).
>>
>
> :-/ sorry. BUT before anything; did you or anyone else succeed to recreate 
> the problem?
>

I ran through a full 1 hour sequence without any error occurring.  In 
addition, I've run the AnalogClock and DigitalClock continuously for *many* 
hours.  The clocks also tick once a second, so if there was a memory leak 
of some kind, they *should* have triggered it.  Again... no errors 
appeared.  If the error still happens for you, try to give as much info as 
possible to help me find the cause.  Specifically, what *other* activities 
did you do during the CountdownSequence?  Did you open/close the clocks?  
Did you pause/reset the Countdown?  etc.
 

> Another conceptual approach: I note that InstantBoss instead functions in 
> another way and which possibly makes more sense: It demands that the user 
> actively dismisses the popup *in order to start the next countdown*. 
> After all, if you're not attentive to the alert, then what's the point in 
> having it continue to count down on your next task? IMO it makes sense: If 
> one wants an unstoppable countdown... then it's just a backward counting 
> clock! Demanding that the user actually starts the next countdown is 
> actually giving control to the user.
>
> BTW, even if you were not to agree with that logic, it is a functionality 
> that I know is useful so I guess it's a feature request then :-)
>

I've just added an *optional* setting to "pause between sessions".  When 
this checkbox is enabled, the CountdownSequence uses a modal dialog instead 
of the "inline message display" to announce the end of each worksession and 
breaktime.  The countdown is automatically paused while the modal dialog is 
displayed, and only resumes when you press the "ok" button.  You can even 
toggle the option while the CountdownSequence is running and it will be 
applied when the next event occurs.

-e

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2aa292f9-2806-47e6-b5b4-584330d2c719o%40googlegroups.com.

Reply via email to