Congratulations, you've discovered state tiddlers. It took me years to discover
state tiddlers. Careful or they'll ask you to write the documentation.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receivi
Ha. I have no idea! It's just what dropped out of the bottom of 2 hours of
fishing around and trial and error!
It did also solve my original problem too around storing the final used
name into a field. Using one of the the same 'dummy' tiddler's fields to
store it and read it back again did the
Nice! A lot more concise.
Correct me if I'm wrong but I believe your optaskstore is a nice example of a
state tiddler.
https://tiddlywiki.com/#StateMechanism
Good luck with the project.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsu
Thanks Watt. In the end I went for another approach, leveraging a single,
temporary tiddler; populating all fields from action-createtiddler
(avoiding all that clumsy action-navigate stuff) and seems to work OK:
!Add Task
--
Task Name: <$edit-text tiddler="$:/_opTaskStore" field="tas
4 matches
Mail list logo
