If you clear the created field in a tiddler, save, and then open it again, you'll see the NaNa... displayed. So this seems to be what the field displays when it is empty or contains text it can't interpret. You can change !!created to !!myfield and then indeed see the literal contents of your macro displayed.
On Sunday, February 7, 2021 at 9:29:43 AM UTC-8 Soren Bjornstad wrote: > While trying to create a button that resets the *created* date on a > tiddler, I absentmindedly tried the following: > > \define now-timestamp() <<now [UTC]YYYY0MM0DD0hh0mm0ssXXX>> > <$button set="!!created" setTo=<<now-timestamp>>> > Created Now > </$button> > > Now, I'm aware this snippet doesn't work and can't be expected to because > the contents of *now-timestamp* aren't wikified when the macro call is > being used as a transcluded widget-attribute value. I've since produced a > correct version. However, I'm still confused about the result of clicking > the button: the *created* field was set to NaNNaNNaNNaNNaNNaNNaN. I'm > puzzled by what kind of calculation the *setTo* attribute of the $button > widget is doing that's able to create a bunch of concatenated NaNs. I would > have expected to simply get the literal text <<now > [UTC]YYYY0MM0DD0hh0mm0ssXXX>> in the field. > > Is there something special about the *created* field in this regard? > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/cde03c17-1470-4edb-9d03-342732372e3en%40googlegroups.com.
