Hi Tobias,
Thank you for this.
Thinking about this issue I realized that if the user opens a tiddler A
for edition, then does something else with some other tiddlers, for
instance clicks a button which changes the value of some field in
tiddler A, and later comes back to the draft of tiddler A and saves the
changes, then the new field value is overwritten.
Example: on tiddlywiki.com create a new tiddler with this content:
<$button>
<$action-setfield $tiddler="GettingStarted" tags="[[new tag!]]"/>
<$action-navigate $to="GettingStarted"/>
Modify tag of GettingStarted
</$button>
then open GettingStarted for edition, and then click the button from the
new tiddler: at this stage the tags in the non-draft version of
GettingStarted contains "new tag!". Now if you close the draft version
by clicking the save button, the tags go back to the previous version.
(additionally GettingStarted is open twice in the story river, which is
strange).
It seems to me that this is counter-intuitive:
- at least I would expect a warning message when I click "save" if some
modifications have been done since I opened the draft.
- or maybe there could even be a warning any time a non-draft tiddler is
modified while the draft version is open?
- an even better alternative, but I don't know if this is possible,
would be to prevent any more editing on the draft before the user
chooses which version they want to keep: either they reload the modified
non-draft version and lose any change done in edit mode, or they keep
the draft changes and lose the other modifications?
- there is also the possibility to synchronize silently the draft
version, but this wouldn't be desirable if the text field is modified,
for example.
What do you think? Should I open a new issue on github about that?
Cheers
Erwan
On 01/12/15 12:36, Tobias Beer wrote:
Hi Erwan,
do you know if it is possible (and how) to make that work with a
checkbox widget and a select widget, instead of a button?
The current approach is to store the selected option at a state /
temporary tiddler
and then use another button widget to actually perform the action.
So, I'm afraid to directly execute the desired action on multiple tiddlers
is not possible today, since non-button-control-widgets are only bound
to a single tiddler.
Technically it's quite doable to bind any of these control widgets to
a *filter*, instead.
*@Jeremy*, would you find this useful? I think it would be,
especially for some utility tool that would batch-modify a bunch of
tids no matter which control is used.
Best wishes,
Tobias.
--
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 tiddlywiki+unsubscr...@googlegroups.com
<mailto:tiddlywiki+unsubscr...@googlegroups.com>.
To post to this group, send email to tiddlywiki@googlegroups.com
<mailto:tiddlywiki@googlegroups.com>.
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/220a8edd-adb0-4bd4-829d-9d3488e2ef00%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/220a8edd-adb0-4bd4-829d-9d3488e2ef00%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/565E3EC7.7080006%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
