Mario, Thanks for sharing "the principle of least surprise <https://www.google.com/url?q=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FPrinciple_of_least_astonishment&sa=D&sntz=1&usg=AFQjCNHdjFIj7fmiE-YiQGyrvd21WY0LVg>" great stuff.
To be clear, since the temp and state tiddlers are automatically "unchecked", if the import mechanism honored checked temp and state tiddler (not deleting them) then the user importing the tiddlers can choose. Am I wrong? This is a functional limitation or bug, whos repair remains backwardly compatible, makes it behave as expected and will introduce new functionality? The functionality we seek is being able to import configurations, or current state. By the way my existing method is making a bookmarklet, this works very well, but it is a practice that must occur outside tiddlywiki in the browser. Are we in furious agreement? A Work around or method could be an alternate import button tiddler tagged with a special system tiddler (I cant find which one) that would allow a full import. Tony On Wednesday, January 15, 2020 at 10:06:40 PM UTC+11, PMario wrote: > > Hi > > I do have a similar issue with the upcoming "stories" extensions. Stories > can be saved and imported. .. I think it should be possible, to import > _and_ activate them, in 1 go, if the user enables importing of $:/StoryList > > I'm OK if the default import mechanism disables everything, that can > create unexpected behaviour. I do like "the principle of least surprise > <https://en.wikipedia.org/wiki/Principle_of_least_astonishment>" but I > also like: The user is in control. > > -m > -- 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/133aad8c-8077-4ac7-8d46-4af0d650b84d%40googlegroups.com.
