> > obviously if only one tiddler in your file contains a particular field > value, e.g., [myfieldname[fieldvalue*1*]], if you use your radio button > to change that tiddler's field value to [myfieldname[fieldvalue*2*]], > then fieldvalue*1 *will no longer appear as an option in the radio button > list. >
Yes, that is true... at which point your ui should also provide a way to add a yet undefined new "type". > For my use case, I found I still needed to create "placeholder" tiddlers > containing the fieldvalues that I wanted to be always available for > selection. > I would think for most usecases it is the best approach to define the options in a precise spot, rather than take them from existing values. However, selecting anything via radio-buttons does not necessarily mean to change any of the tiddlers from which the options were constructed. It only means to make a selection, perhaps for some dependent ui that generates desired output. So, the radio button would actually set some state or temporary tiddler. 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
