That command essentially nudges everything apart slightly. I’ve not seen it OMM< but I guess sometimes the nudge isn’t quite enough.
Hi Ralph,
Using agents to create a map view is a solid approach. Alternatively, tools like Concept Map Maker can simplify presenting systems, changes, and dependencies on the same level.
Hope this helps!
@Krish , are you affiliated with Creately? (You’ve posted recommended their product before.) If you could explain how the Creately product would integrate with Tinderbox, it would be helpful information for the community.
Perhaps. My experience with this approach is any map view design I’ve done gets reset when the agent updates.
You can certainly turn the agent off by setting $AgentPriorirty to -1, or if the approach is to use the agents to find relevant notes, you copy the discovered aliases into another container; then you don’t have the issue of the map view getting reset; but, this prompts other consideration
Set the agent’s $CleanupAction to "" (i.e. nnothin/no value) to tell Tinderbox that you don’t want it to arrange the notes in a neat grid.
1 Like
Thanks Krish, for your remark regarding concept map maker. My personal preference is to stay in one tool and to avoid switching between tools in my working process. From my experience, switching tools is costing me a lot of time and it breaks my focus.
My actual way to work is to create a group of aliases for the map and turning off the cleanup action as mentioned. At this point, dependencies between notes are recognised and stable and the map is a kind of documentation for me or I share this documentation with others.
For the active analysis of notes and their relationships, I have learned to use the out-of-the-box views of Tinderbox, which are much more useful than I have thought before.
1 Like
Great to know. BTW, I check aTbRef, and it notes that the value of "none’ will suppress the cleanup action. Good to know that a null value may as well.