Oh, that was quick! I'll try this out and post a reply as soon as I'm done fiddling. I'm unfamiliar with the SET widget so it'll probably take some time for me to understand the internal process.
About the buttons. I also wanted them to always be shown, but ran across the problem of accidentally clicking them during testing... I wonder if there's a quick way to set them to "disabled" or something. I know this one's solvable via html and CSS, I'll google this one! On Wednesday, November 8, 2017 at 10:14:42 PM UTC+9, Jed Carty wrote: > > I have a few things that may be useful: > > 1 - if you know what fields you are going to care about than you can make > a list that will display them all doing something like this (it is a bit > messy and I haven't tested it, but the general idea should work): > > <$list filter='[[fond-title]] [[font-h1]] [[font-h2]]'> > <tr> > <td>Heading h1:</td> > <$tiddler tiddler="TIDDLER A TEMP"> > <td><$edit-text tiddler="TIDDLER A TEMP" field="font-h1"/> > <$reveal type=nomatch state="!!font-h1" text=""> > <$button> > <$set name=CurrentValue filter='[[TIDDLER A TEMP]get<currentTiddler>]'> > <$action-setfield $tiddler="TIDDLER A" $field=font-h1 $value=< > <CurrentValue>>/> > </$set> > <$action-setfield $tiddler="TIDDLER A TEMP" $field=<<currentTiddler>> > $value=""/>✓</$button> > <$button> > <$action-setfield $tiddler="TIDDLER A TEMP" $field=<<currentTiddler>> > $value=""/>✕</$button> > </$reveal> > </td> > </$tiddler> > </tr> > </$list> > > 2 - I have found that it is also always a better idea to have the values > you are editing in another tiddler. Never edit the fields of TIDDLER A from > inside TIDDLER A, always use some interface tiddler to edit fields in > TIDDLER A, or have some other tiddler like $:/settings/TIDDLER A with the > fields you edit and then have TIDDLER A reference those fields. I have > found this makes my work much tidier and easier to understand later. > > Another note about buttons: In my experience it is a nicer if you always > have the buttons visible and just change the colour when they don't do > anything instead of making the buttons disappear. Either move the reveal > inside the button widget so that the buttons are always there but only act > if there is an action to do, or put a second reveal that has the opposite > condition that displays a dummy button that is greyed out. > That may be more of a personal preference for me. I am dyslexic and having > controls disappear and reappear can change the layout of a page and it is > hard for me to follow that. > -- 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/a16d3fa6-b2ff-4487-a1c0-25e27cd7d252%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
