I am looking for a way to merge branches together in a well stuctured way.
Please see in the screenshot what I tried by using connections. In principle, this satisfies my need but it does not look quite good ...
What I want to have is something like this:
Is there a way to achieve this?
Thank you, kind regards!
You can select the relationship line and use the yellow handles to place the relation to the desired side of the topic
You can select all relationships to Prime nrs and format them in one go.
It can be done although it is a bit of work
Thank you very much for you quick help, Ary! It is a good solution for my task!
Just one last question: Is there a way to create these connections in a more automated way like done when creating a top-down mindmap tree? The standard connection seems to be also a little different, since there is a (-) to click on to collapse etc.
From Req as well as from Prime/even nrs .
The mindmap technique was not designed for that purpose. That is always a tree, hence the + and minus when creating and collapsing a tree. And that is why you need to use floating topics and connect them through relationships to get the image you want.
You would need something like conceptmaps for your needs.
They can be made by using this Addin http://www.olympic-limited.co.uk/product/network-builder/
Maybe I shall explain a little bit the purpose of what I wanted to do: It is a kind of a system architecture for an electronic device. The device shall meet several requirements. Main requirements are split up into sub requirements and subsub requirements. This fits well into the tree structure of a mindmap. But this is not where I wanted to stop. I would like combine the subsub requirements again in another (logical) way to "functional groups", that one can easily see which functions cover wich subsub and sub requirements. Any good ideas on how to do this in MindManager?
I did a test with Michael's idea of using TAG's and MAP-Index functionality
It provides the insight as N Strach describes, but ofcourse not the visual that emonterog wants.
No need for floating topics though.
I personally think the visual is another issue, and moving a bit away from Mindmaping conventions, but absolutely nice to have.
Right now the only way to 'close' a branch would be to put a boundary on it...And then a boundary can have a callout and then the callout can have additional children. This doesn't work elegantly at all but it does, very roughly allow multiple children to be summarized by a topic. I like the idea that you're mentioning above though and you're not the first to ask for it.
Floating topics are floating because they do not belong to other topics. Neither as parent nor as child. You can either drag them to a parent,( but then they are not floating anymore) or use relationshiplines to inform you there is some kind of relation. That is why there is no real association. Floating topics are a real gift while e.g. brainstorming
By the way, have you found the Balance Map function in MIndManager to re-distribute your topics ?
Have you seen the little white circle that comes with a topic that can be used as a handle to place the topics etc to any desired place on your canvas? (it turns black once the location is changed) You can hold down he shift key while dragging (as Michael mentioned) to be more precise.
Have you seen the vast amount of templates and design features to optimize the look of your map's?