Facilitate multiple parent nodes
When two ideas converge to form a new point that needs both parents. This is different to just connecting two arbitrary nodes together. It might require a reorganization of the map layout to keep it looking neat.
you can now add multiple roots, disconnect nodes and float them, and manage multiple maps in the same file on mindmup 2.0.
If you use google drive, use https://drive.mindmup.com
if you use free storage or Gold storage, use https://app.mindmup.com
-
Simon Holmes commented
I don't think this is completed in the way most of us meant. Here is another version of this idea that has a decent number of votes - so if we reallocate our votes here the developers should be able to prioritise it. https://mindmup.uservoice.com/forums/200447-what-should-we-focus-on-next/suggestions/7790775-merging-two-separated-nodes-into-one-by-connect or if there is a better one please let me know
-
Tiago Sousa commented
I agree with Bruno: multiple parent nodes != multiple roots.
-
Bruno commented
Hello,
I think this need was misunderstood and it is not completed.The need for this feature is different than:
https://mindmup.uservoice.com/forums/200447-what-should-we-focus-on-next/suggestions/4391924-i-would-like-to-have-the-posibility-of-starting-moMaybe the David who has proposed this idea can correct me but what it was asked, to have the capability to link a child element to more than one parent. This feature refers to "Multiple parent node ability" that, to my knowledge, only one software offer it, not to name it. Look at wiki page https://en.wikipedia.org/wiki/List_of_concept-_and_mind-mapping_software. Search for the exact terms "Multiple parent node ability".
Please look at this image in my note:
https://www.evernote.com/shard/s158/sh/ac18ed41-2381-4000-9181-1d33f6a8568d/a2a2e5b453e5f7669026b1546b0e4488Hope this help. Contact me if you need anymore information.
Thanks.
-
Anonymous commented
+1
-
Mirjam commented
+1
-
Rahi commented
Is this idea related to the following?
-
Katie commented
The ability to indicate multiple parents provides the opportunity to indicate multiple paths to a single idea without repeating the majority of the information in a separate tree. For example, I'm currently mapping out what courses I need to take for a degree. Say one course offers 3 courses that can be substituted as prerequisites. To visually represent the reality in the current single parent structure I would have to lay out three separate trees. Ideally I should be able to indicate three parents (possible course prerequisites) to a single node (the target course). This could be represented as a parent and three children if you read the tree backwards, but becomes impossible to read if any further courses are included especially if they too offer multiple prerequisites or "parents"
-
Nauman Mithani commented
I too would like to vote for this where multiple nodes can have one common child node.
-
Adrian Kerry commented
Heidl - there are situations where it's useful to present two trees on one diagram.
In my example I have a series of symptoms and they seem to stem from two route causes. I want to show this on one mup.
-
Heidi van Schaik commented
So logically, the new child node is equally the child of two parent nodes. Therefore, it would be incorrect to attach the child arbitrarily to one parent while arbitrarily using the connector to express the attachment to the other parent.
I suggest that there be an extension for this, where you specify how many parents the selected node has. You can now drag the child node over to its other parent, and a new parent-child connection will be made, without breaking the original parent-child connection. I don't know how hard it would be for the app to draw; probably as hard as the curved connector lines we don't yet have.
On the other hand, is it possible that the new child node is actually the parent of the two supposed parents? I think this is possible, but probably not true in all cases.