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?
One thought: I recall these news 
<https://www.techradar.com/news/chromes-new-feature-will-stop-tabs-from-eating-all-your-ram-heres-how-to-try-it>
 about 
Chrome some time ago which kind of deactivates unused tabs to save 
memory... might that have sth to do with it? (I have not hit the ceeling in 
memory usage during these tests, at least nothing I've noticed.)

 

>  I need to look into this a bit to figure out how to programatically 
>>> dismiss an existing modal.
>>>
>>
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 :-)

 <:-)

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/baa67ea8-2cd1-444e-b762-cfb5597c233bo%40googlegroups.com.

Reply via email to