Somewhere I have some experiments with something like this. A much safer alternative is to have a background daemon running that emits some event every so often and use that as a clock, then your widget counts pulses (or waits until after a specific time) and then acts.
So you could have the background daemon emit a pulse event every second, then you have an action widget that will count a certain number of pulses before before running the action widgets that it contains. I hope that makes sense. I have run into a few cases where this would be useful for me in the last few days, but I am not sure how long it will be before I will have the time to make it. Alternately you could go the easier route and just use a setTimeout in the widget that waits however long you want before running the code. That is how the background daemon would work anyway, the only reason to not use that is that the time would only be accessible inside the widget instead of a globally available clock. -- 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/ddba697e-3509-4dc7-890b-7e917523ed6e%40googlegroups.com.
