A sign that a node has been mirrored!
CompletedWould be super helpful to have some kind of subtle sign or mark indicating that a node is mirrored in some other places.
Sometimes I might delete an original node because it doesn't seem to be relevant anymore, but it might be relevant in their mirrored instance in other parts of the tree structure.
So, before deleting an original node that is mirrored it should be essential to:
- know that the node is mirrored in other places!
- Know where those mirrors are, so we can decide if we delete the original node (which will automatically delete all its instances of the node, or if instead we just better move the original node where it was mirrored.
This would delete the node from its original place but will allow us to keep the content where the mirror was.
Hope the explanation is not too confusing and makes sense!
-
Is there any reason why there has to be a "master node"? It seems arbitrary to me. What if ALL mirrored nodes had the same icon even if they were the "master". Then each can simply be deleted individually by default with WorkFlowy automatically doing whatever it needed to in the background to move the master status around (if that's even necessary). Then put "delete all mirrors" as a special delete option, thus making deleting a lot of data not the default option.
It's simple, clean, effective, and naturally protects data.
-
Hi Alfred,
I think you have a very good point there, and that might bring the proper solution to this issue.
I would only add the ability to see where all the mirrors are located in our tree structure.
This could be a small text under the 3-dots menu* of each of the mirrors.
* As where the "mirrored node - view original" is right now.
-
Hi Alfred,
So, as seen on just another WorkFlowy forum, if you go now to https://beta.workflowy.com/ and in the settings menu toggle on the switch to enable the function "Equal Mirrors", it will make the original look and behave the same as mirrors!
I think this is exactly what you suggested it should be :)
Hopefully, this behaviour should be coming soon as a standard in the non-beta app and the Mac OS desktop, too.
Cheers!
Please sign in to leave a comment.
Comments
6 comments