Hi Team,
Our use case: We want a set of adornments to be visible on nodes on diagram load and stay, then we control the adornments using the visible key which adornments to be visible and which to hide. The arrows are the adornments in the below image.
From what i gathered from other topics like Permanent adornment with indicators ,
It seems like making them part nodetemplate instead of using adorments and using the selectionObjectName is the way to go.
Please let me know if there is a better way to achieve this using adornments? Also please mention any limitations of using selectionObjectName to avoid unexpected behaviour.
Yes, there is a wide range of implementation possibilities when there are so many possible behaviors.
If you want some number of decorations to really be a part of the node, then putting them into the node template makes the most sense.
If you want nodes to fundamentally be a particular size, ignoring any possible decorations, then using Adornments to implement those decorations makes sense.
Did you want to have (say) five different types of decorations, and then did you want to control the visibility of all Adornments corresponding to a particular type of decoration for all Nodes at the same time? Or did you want to control which decorations are visible individually for each node, with perhaps many nodes all showing some desired different subsets of decorations?
In the former case, is there basically a global variable/flag controlling the visibility for each of the types of decorations that you might show?
In the latter case, is there a data property on each node controlling the visibility of each type of decoration for just that node?
