Thanks Jed, a timer could be used to create a daemon and write the state to a tiddler a few times a second, - the next issue would be that writing this data should not cause a refresh - we could have a tiddler namespace ($:/__priv__/ maybe?) that would not be refreshed.
On 24 January 2015 at 12:26, Jed Carty <[email protected]> wrote: > Would creating a daemon to track the state for the player work? I am not > sure how the mechanism works internally, but they can at least have > internal timers that aren't affected by widgets being refreshed, so it may > not have the same problems with losing information when tiddlers are > rerendered that widgets do. If that is the case than you could have a media > player daemon that starts when the media player is loaded remembers the > players status so any widgets can get information from it when they are > forced to refresh. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "TiddlyWikiDev" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/tiddlywikidev/et0wVg-J6Gw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/tiddlywikidev. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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 http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
