Just some observations.
My proposal used a modified Save tiddler with
<$action-sendmessage $message="tm-close-tiddler" $param=<<currentTiddler>>/>
inserted after
<$action-sendmessage $message="tm-save-tiddler"/>
I thought saving of the tiddler occurs *before* closing of the tiddler, so
no draft situation when you close it.
But neither `$param=<<currentTiddler>>` nor `$param={{!!title}}` does work,
although a hardcode parameter `$param="New Tiddler"` does save & close New
Tiddler!!!
Maybe I tested my hardcoded version when I proposed my Save & close button
;-)
Eric tried `param={{!!draft.title}}` which did not work either.
RichardWilliamSmith used a separate variable for the draft status:
<$set name="ogtiddler" value={{!!draft.of}}>
and
$param=<<ogtiddler>>
which works. Thanks Richard.
Conclusion: With a hardcoded `$param` you do not need the draft status, but
with a softcoded `$param` you do need the draft status.
So a hardcoded $param acts not the same as a software coded $param. But why?
@Julian
Create a tiddler which contains:
{{!!title}}
{{!!draft.of}}
{{!!draft.title}}
In edit mode with preview mode enabled you see that `{{!!draft.of}}` and
`{{!!draft.title}}` behave the same.
But - still in edit mode - change the title of that tiddler. Only
`{{!!draft.title}}` follows the change! Why?
As I said: Just some observations. Maybe somebody can explain my
observations.
Cheers,
Ton
--
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/a7d81dfb-7789-4619-ba7b-f1ccbf2e853a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
