Hi Mans I am open to suggestions. I have debated whether to retain the set and setTo attributes of the <$maketid> widget myself (they are a legacy from the <$linkcatcher> widget which was my template for developing both the <$seffield> and <$maketid> widgets.)
The set and setTo attributes of the <$button> widget can take care of state variables (this must be the primary reason for their existence.) The set and setTo attributes of the <$maketid> widget appear somewhat redundant (and clearly create confusion.) Should they be retained? Can anyone think of a use for them (remembering that they target 'currentTiddler' by default), or should they be removed? regards On Saturday, May 31, 2014 5:50:37 PM UTC+2, Måns wrote: > > Hi Matabele > > Thank you for explaining things :-) > > Sorry if I'm still confusing things however: > > I'm not sure if I would prefer that: > > >the set and setTo attributes of the <$maketid> widget could be removed > entirely (after all, a <$setfield> widget is easily added.) > > You can't have more than one set of set and setTo attribute in one > <$maketid> call - or can you? > Isn't that why you introduced the <$setfield> widget in the first place? - > or is it because <$setfield> is more "generic" ? (eg. can be added to the > button macro)... > > I hope you will excuse my obvious confusion in these matters - however I > haven't tried to create widgets or plugins myself - for a reason .... > > Cheers Måns Mårtensson > -- 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.
