I and Mark Anderson have separately explained to you what appears to be the problem, and have provided several ways to fix it. None of this appears to be anything other than Tinderbox doing what you have told it to do.
If you would upload a copy of your document, we could better understand your difficulty.
Understood. I know Tinderbox is doing exactly what I have told it to do. 100%.
I also know we miss each others’ meaning because I do not share your language (which is why I generally cannot understanding mwra). I also appreciate it is difficult saying things without using that language, single terms that encode multiple layers of meaning/nuance, but that I, a beginner, simply do not know. Knowing something yet explaining it so a 5 year old can understand it is challenging (I understand the challenges and appreciate the efforts). But the upshot, unfortunately, is I am unable to understand. I want to understand but I will not be able to hear or communicate in your language.
Perhaps the following will help you better correct where I am mistaken. If my incorrect terminology makes your understanding difficult, please be generous. If my terminology makes your understanding impossible, please ask for clarity and I will try another way. TIA
I create a note which I make a prototype
I ‘attach’ an agent to that prototype note
that agent will create an alias (will copy the note) every time I choose that prototype
all of those aliases/copies will be delivered to one container on my map
it is possible to attach more than one agent to a note and have the same alias appear in more than one container (not relevant to my current problem but to test my understanding)
I will be able to locate those aliases in their designated container
Issue:
I have done “X” such that creating a new note and using that one prototype (and only one) causes that note to “disappear” from my map view. We have determined:
the note has not disappeared; it still exists as it is in my note pane on the RHS of my screen (in both map and outline view)
in map view the note is not appearing in its container
in outline view it appears in two places: at top level (which means I should find it on my map view top level) and in its ‘container’.
in outline view there are a LOT of notes showing in this ‘container’ that are not showing in map view
point 3 also means it should be appearing in the map view container, correct?
I do not see the note on my map view top level, assuming it is not ‘hiding’ behind something else in map view. Please advise if it could be behind something else on the map and I will look.
Definitely don’t delete anything. Better is to start a new TBX alongside the old one. Tinderbox allows you to have as many discrete TBXs as you like, even if most people only have one or a few.
If your file is too personal to share publicly, I’m happy to take a look privately. If so DM me here. This will route around the issue of what appears to but entirely unintentional lack of a common perspective/terminology. Seeing a file underlying some of the problems described would aid that massively.
Leading a new tool, especially an open-ended toolbox like Tinderbox can appear daunting but I think that generally stems form the lie we are taught that everything should be intuitive’ (though even that term is left ambiguous.
But, don’t rush to delete anything out of frustration!
Most likely—I can’t be 100% certain as I don’t know the complexity of the content. Also, as your existing document has issues, it would be a better approach to make the new one the long term document. this flips the task; avoiding content that seems to be bad.
Also a really good practice to acquire is that, when trying a feature new to you, make a small Tinderbox to test how it works. Indeed, it’s a good idea to aim to throw away the document when done having applied the techniques tested in the small file to your real work file(s). It might appear extra works. But, this way you can make a complete mess of your first experiments at zero risk. Just start over, even with a new file if needs be. When you’re happy with how things work, you’ll be more confident using the ideas in your true work files.