On Wednesday, July 29, 2020 at 6:15:19 AM UTC-7, Mat wrote: > > Eric Shulman wrote: >> >> 1) RSOE >>> >> I have not seen this error, and I've run through the whole sequence of 5 >> work sessions/break times (with shortened times of 1 minute work and 15 >> seconds break). Can you tell me more about what happened? Can you >> reproduce it with the latest version (just updated to add configuration >> controls) >> > > Yes, having tried it now several times I do get it to happen repeatedly in > the latest version: I just leave the default(!) values and start the > countdown and let it run while I do other stuff in other tabs. I do peek > back every now and then to see how things were going. Unfortunately I can't > say after exactly how long time it happens but my best estimation is after > some three sessions. Not faster. > I'm on Win10, Chrome. >
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). > I need to look into this a bit to figure out how to programatically >> dismiss an existing modal. >> > > Perhaps worth considering that they don't *have *to be modals. Just > sayin'. Apropos modals, here's > <https://css-tricks.com/pseudo-element-roundup/#fade-out-a-page-when-a-particular-link-is-rolled-over> > > an interesting css based variant- basically the thing you want to show has > a pseudoelement beneath it with dark color that covers the whole screen. > (...or maybe that is exactly how a ... > I did some experimenting, and it doesn't look like modals can be programmatically dismissed. Some alternatives I can think of: 1) Use tm-notify to put up the message. These messages automatically go away (by default, after 3 seconds). My concern is that the message might not be as noticeable. 2) Don't use ANY TWCore message, but simply write the status into a separate tiddler. Then, just transclude that tiddler's content somewhere (maybe with an ok/hide button) 3) Possibly combine (2) with a modal-like display. Since the tiddler in (2) would be overwritten each time, the previous display would automatically vanish. Stay tuned for another update... but it might be a while. These last few problems are tricky! -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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/81be8741-b497-44fc-b123-d8e5264c67e6o%40googlegroups.com.
