Tony, Here's one totally non-representative example:
1. When I log a new running/cycling workout, I select some options and then click a "Log" button. 2. This button initiates a sequence of actions (a stack of action widgets), the last of which is a fancy animated notification. 3. However, when I'm on mobile, my fancy animated notification "Workout logged" is not animated, because my phone is still overwhelmed after running all the previous actions. 4. So what I've done now using Jed's plugin is wrap my notify action widget like below. Now the notification still shows nicely on mobile, with animation and all, because the 2 second delay was more than enough for the processing power to "recover" and for my phone to render the video (CSS) effect properly: <$action-one/> <$action-two/> <$action-delay delay="2"> <$action-sendmessage $message="tm-notify" $param="_notify_logged"/> // Delayed action </$action-delay> There are many other examples where you can spread out actions over time, we're no longer confined to firing everything this instant. One (probably not a useful one) example could be to show an alert and then close it 5 seconds later. But again, it all depends on the problem you're trying to solve. Hope this helps. Regards, Hubert On Thursday, 7 May 2020 14:06:59 UTC+1, TonyM wrote: > > Could those in the thread explain to a broader audience what such a > function would do for us and or a use case? > > thanks > Tony > -- 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/2790a690-b30d-4f23-a01a-1047e7452655%40googlegroups.com.
