On Sun, 17 Jun 2012, PMario wrote:
If I enter a space, it seems the SystemSettings tiddler is created by the system in the _private bag. If I allready have a _public SystemSettings tiddler it messes up this space.
SystemSettings has been saved to *_private for at least two years now: https://github.com/TiddlySpace/tiddlyspace/commit/16138472146b0742cb28003df603ca8bdbcd8395 I'm not sure of the details but I think the expectation is that SystemSettings for a space will be created immediately after space creation
It also heavily conflicts with the space include mechanism. Several of my plugin spaces are broken. A public SystemSettings tiddler is a shadow tiddler if it is included with a space. .... the core mustn't change it.
I suspect the problems you are seeing are entirely in the domain of TiddlySpace plugins, and not the core. If we can determine that's the case then we should move this conversation over to [tiddlyspace] instead of here. Can you explain in more detail what you mean by "conflicts with the space include mechanism". It's not clear what behavior you are trying to achieve nor what is going wrong. If you are trying to use SystemSettings in space A to influence in space B, that's probably not the way to do it. It's pretty clear there is a bit of logic problem in the code somewhere but I've never been too clear on how/when SystemSettings was supposed to be created (in or out of TiddlySpace) to know what's right. I do know that on occassion when I visit a space of which I'm not a member it will try to save a SystemSettings tiddler and fail, which shouldn't be happening. But the pattern is not regular. -- Chris Dent http://burningchrome.com/ [...] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
