Si, Is there a technical reason to store the "count" and "last" values in a > totally separate tiddler? It seems like it would make more sense to store > them directly as fields in the actual tiddler that they relate to? >
This is what I was thinking about, plus the counters will be lost by renaming the tiddler. On the other hand, they are not tied to the tiddler itself, but rather to the wiki. For example, if you import a tiddler that has a counter into another wiki, that counter in the other wiki becomes meaningless. In this solution (setting the tiddler's own field), I don't even like that the "modified" field changing after each opening of the tiddler, since its "last" and "count" fields would always change, so the "last" field could be completely omitted and only the "modified" field should be monitored. This reminds me that this would also modify system tiddlers by default. -- 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/deb4dad3-96be-4329-9c09-b191dd4cc7e0n%40googlegroups.com.
