On Wednesday, July 29, 2020 at 7:55:46 PM UTC-7, TW Tones wrote: > > > - What function do you see the pause-able clock playing? > - One could click it when starting work and review it > - But I wonder if you have another idea in mind. > > At it's basic level, each instance of the clock (analog or digital) adds a once-a-second repeating interrupt that writes to a $:/temp tiddler. If there are multiple instances, there are multiple interrupts occurring. While this is not a lot of overhead, it's conceivable that there might be a situation where this overhead could have an effect on performance of some timing-critical processing like animations or streaming high-bandwidth video, or some such use-case. It just seems reasonable to have a way to toggle the clock interrupts if/when it becomes necessary to do so.
> Feature request > > - Perhaps this already possible, but is it possible to trigger some > actions defined in a tiddler or macro when a timer completes? > - I ask this because then any set of actions can be triggered. > > The general-purpose Timer/Countdown invokes a tm-modal message display when the timer completes. The SampleCountdownSequence doesn't use tm-modals, but does create a tiddler containing a message, and then displays that tiddler content inline. The new Timer/AutoSaver (just wrote it tonight!!!) invokes a tm-save-file message to actually save the file. In general, any set of action-* widgets could be fired off when a timer completes. Perhaps I can add a way to specify an optional tiddler title that could contain action-* widgets to be triggered by the general-purpose Countdown timer. > > - One could send a message to save 15 mins after the last save or > regularly. > > This is essentially what the new Timer/AutoSaver does. It sets up a timer "loop" that periodically performs a tm-save-file action. The default is once-per-hour, but it is configurable to suit the work patterns of individual users (i.e, some people might like to save every 15 or 30 minutes) > > - Or in startup set a count down to open a modal 10 minutes > > I haven't thought about triggering a Countdown timer on startup... but it shouldn't be too hard to implement. The basic Timer/Countdown expect user interaction to trigger the start of processing, but a simple set of action-* widgets could be used at startup to create an appropriate $:/temp/timer/* tiddler with the right fields to specify the hours, minutes, seconds, go flag (set to "go" for "autostart"), and done (the action to perform when the timer completes) > > - Perhaps even a timer to save and logout/check in after 30 minutes of > inactivity > > I'm not sure how we would determine "inactivity". This solution really benefits from you being the author with you extensive > knowledge, because timing solutions can kill an app or software, if not > done correctly, so this is greatly appreciated. > Aw, gee. Shucks! Thanks for the nice words. -- 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/2c58df83-c17b-4298-a529-3e48f9b442d2o%40googlegroups.com.
