Replies: 2 comments 7 replies
-
Hmmm, At the moment ActionCreateTiddlerWidget is the widget, that doesn't navigate by design. I did add new functions to action-create, since it didn't have the same features as tm-new-tiddler. ActionSendMessage $message="tm-new-tiddler / tm-edit-tiddler" is the action widget, that does navigate. see: https://tiddlywiki.com/#ActionSendMessageWidget |
Beta Was this translation helpful? Give feedback.
-
Action-widgets have been created, because the button-widget was completely overloaded with features and parameters. It got more and more complicated. IMO in the end it was hard to use for "standard users". Action widgets are designed to do "a few" things well, so they are easy to combine to do more complex things. |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
It is unclear how to directly navigate to a tiddler created with the ActionCreateTiddlerWidget because the new title of the created tiddler is dynamically numbered.
Describe the solution you'd like
I wish for a
navigate
attribute. If this attribute is set tonavigate=edit
ornavigate=editmode
, one is navigated to the edit view of the tiddler. All other arguments navigate to the viewmode of the tiddler.The idea to avoid an explicit argument for the latter is because it is difficult to remember it: "What is the opposide of edit view? "View view?" We do use "edit mode" and "view mode" but I propose that anything should go e.g
=view
=viewmode
="view mode"
=yes
=true
. (Maybe even no argument i.e just the attrbutenavigate
.)Beta Was this translation helpful? Give feedback.
All reactions