Eric, Sorry, one more point.
In some cases we do not need to keep the time start and end history, and the total time work can be added to the previous total. I imagine for example having a sidebar with a set of elapsed timers where one would click while working on correspondence, phone calls, coding, customer relations social media etc... Saving total for at the end of day in a journal tiddler, but starting afresh each day. This would support a range of productivity methods suggested in time management and productivity methods. I think I can build this on top of your solution already, but thought I would share what I would possibly want to do once this is published. Thanks Again TW Tones On Thursday, July 30, 2020 at 12:55:46 PM UTC+10, TW Tones wrote: > > Eric, > > I was just reviewing the state of play on your timer work. It really is > fantastic. These features have being long sort after, a question and a > feature request if I may. > > Question > > - 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. > > 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. > - One could send a message to save 15 mins after the last save or > regularly. > - Or in startup set a count down to open a modal 10 minutes > - Perhaps even a timer to save and logout/check in after 30 minutes > of inactivity > - I assume we can just reset the value to restart the count down > when we save. > - Not unlike your SampleCountdownSequence one could use a timer > action to trigger another timer action > - This a set of tiddlers with expected times eg a calendar could > trigger and action/message and set the next timer on the next > tiddler. > > 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. > > > Regards > TW Tones > > > On Thursday, July 30, 2020 at 10:49:49 AM UTC+10, Eric Shulman wrote: >> >> On Wednesday, July 29, 2020 at 8:20:18 AM UTC-7, Eric Shulman wrote: >>> >>> 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. >>> >> >> updated http://TiddlyTools.com/timer.html >> >> * TiddlyTools/Timer/SampleCountdownSequence now uses a custom message >> display instead of tm-modal (solution #2, above) >> * improved "start" button logic to disable button when time values are >> all zero or countdown is actively running >> >> Next... try to figure out where the memory leak is in the $action-timeout >> widget. This may be a really hard problem to solve. >> >> -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/7ba8f6b1-0f06-4b60-9216-d687c6f5601ao%40googlegroups.com.
