> > <$set name="tid" value="""""" default="<<currentTiddler>>"/> > > So, there's an empty string being passed as the attribute "value". There's > no way for the set widget to distinguish that empty string as a missing > value that needs to be defaulted unless it regarded all empty strings as > missing values. The trouble with that is that often we want to be able to > assign an empty string to a variable. That could be accomplished by > assigning the empty string as expected if the "default" attribute is > missing. >
I totally understand that, my suggestion was to alter the actual text substitution so as to pass down a literal "*<<underfined>>"* or "*<<null>>"* or any appropriate flag as a *string*, which of course would not be possible for use as an actual value. So, instead we would be left with... <$set name="tid" value="""<<undefined>>""" default="<<currentTiddler>>"/> ...and the appropriate handling by the set widget. Not if *<<undefined>>* provides for a naming convention but something that doesn't leave us with an empty string... and widgets by default treating all of *<<underfined>>*, *<<null>>* or *<emptyString>* the same, except for when explicitly declared otherwise. 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.
