The timer itself should barely use any resources, particularly compared to the browser or even just the wiki. Setting the update timer to longer intervals will probably have no effect on performance as long as it is significantly shorter than the period for the actions, otherwise the timing between the actions can be inaccurate. The savings from making the update interval longer are almost certainly going to be lost in the normal variations of power usage by the browser. The analytics built into many websites take much more energy than this, if you want an example. I have given up on trying to figure out what is generally considered intuitive or simple. I can add a quick table to it. I briefly considered writing something so you could give times in other ways but got bored before I wrote or found a parser for it. Next time I feel like looking at this I can see about adding a prefix but that leads to more annoyance than I want to think about now if people use something other than the simple interface I made to make timed events and give them different prefixes.
-- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/6a841be4-2f95-4d50-82b3-b7116881977f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
