Did you test it with 1 field first? -m On Friday, July 9, 2021 at 4:27:39 AM UTC+2 Ed Heil wrote:
> Thanks, Tones. I will be interested to hear it when you are ready to make > your plans public. > > I've been working on the "edit in a temp tiddler" thing and made some big > ugly macros that do the job swimmingly. I should be able to get the app > converted over to using temp tiddlers for editing, in general, soon. > > On Thursday, July 8, 2021 at 3:43:11 AM UTC-4 TW Tones wrote: > >> Ed, >> A long answer is there are ways to edit the current tiddler, even without >> a temp tiddler. I am building a solution which does this now, it involves a >> little gymnastics and is hard to explain with too many different aspects to >> it. I will eventually publish something. >> >> One handy way is to have a tiddler dedicated to editing other tiddlers. >> In there you select the tiddler you want to edit, and all your editing >> takes place on the not visible selected tiddler. >> >> Regards >> Tones >> >> On Wednesday, 7 July 2021 at 23:25:01 UTC+10 Ed Heil wrote: >> >>> This is all great info, and clearly what I need to do. I didn't realize >>> that there was special behavior for $:/temp tiddlers with respect to >>> saving. (The only mention I can find on tiddlywiki.com is in "Naming >>> of System Tiddlers" which I thought was just about naming conventions, not >>> names which trigger special behavior.) Now I've got to figure out whether >>> it's doable to fix my app piecemeal -- which has tons of editing fields >>> which act directly on the tiddler they're on -- or whether I need to >>> somehow start over with a temp-tiddler-based editing flow. Ah well. You >>> live and learn. >>> >>> Thanks again for pointing me at $:/temp. >>> >>> >>> On Tuesday, July 6, 2021 at 2:09:13 AM UTC-4 PMario wrote: >>> >>>> uups forgot something, >>>> Clicking the [OK] button will work the other way around. Clone temp -> >>>> form and delete the temp. >>>> The edittext-widgets tiddler parameter will need to be a variable. ... >>>> depending on which tiddler is active atm. form or temp >>>> -m >>>> >>>> On Tuesday, July 6, 2021 at 8:06:28 AM UTC+2 PMario wrote: >>>> >>>>> On Tuesday, July 6, 2021 at 4:29:30 AM UTC+2 Ed Heil wrote: >>>>> >>>>>> Thanks, TW, PMario. What defines a temporary tiddler for these >>>>>> purposes? Being under $:/temp/ ? >>>>>> >>>>> >>>>> Yes. ... It depends how your form looks like and how the tiddler you >>>>> need looks like. I would define a view-mode for the form, where the edit >>>>> fields are not active, but show the content of the "form tiddler". This >>>>> can be done with the "disabled" parameter since 5.1.23. ... >>>>> >>>>> A button eg: [Config] will copy the "form tiddler" into the "temp >>>>> tiddler". If the temp tiddler exists, the "disabled" state will be >>>>> switched >>>>> to "no" and the values can be changed. [OK] [Cancel] buttons that >>>>> replaces >>>>> the [Config] button will be shown. >>>>> >>>>> Cloning the "form tiddler" can be done with ActionCreateTiddlerWidget, >>>>> which has $template and $overwrite params since 5.1.22 >>>>> >>>>> A disabled filter can look like this: disabled={{{ >>>>> [[$:/temp/form]is[tiddler]then[no]else[yes]] }}} >>>>> >>>>> hope that helps >>>>> -mario >>>>> >>>>> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/4f276966-0c36-4c63-8243-c651cd3fe25en%40googlegroups.com.