Aaron, My suggestion includes how I would do it, I believe it would be easy to maintain a last modified date for each field if you desired, but you would need control the methods used to modify the fields so your field timestamp gets updated.
The design concept I have should not add complexity to your templates only "the methods used to modify the fields so your field timestamp gets updated" But if you are content with the current solutions, we have no need to go down this path. Regards Tony On Thursday, February 6, 2020 at 3:52:36 AM UTC+11, Aaron Haslem wrote: > > Eric, > Thats awesome! I can work with this. Already have other ideas for how to > use what you are showing here. I am not a code person, so I did not > realize the $id$ use as a means of using and passing a variable. Thanks! > Very handy. > > Tom, Yes. From Eric's responses I came quickly to the conclusion that > there was not a dedicated modified date for fields. Your method sounds > interesting but, I use a lot of template tiddlers (as I will with this use > also) to display information in a uniform manner. In this instance, I > would think that having a dedicated system tiddler keeping track of the > modified date would make juggling several dozen tiddlers, all using the > same template, a little difficult....unless Im not understanding very well > the concept you are proposing. > > Thanks for the input Gents. > -- 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/ee1983a9-db59-4d56-a33d-31decf3c1851%40googlegroups.com.
