Hello, I maintain several collections that have a shared "central" config. For all of them, when I drag a new node onto the palette, the new node never defaults to the already existing configuration, it always reverts to "None". I could have sworn the behavior used to be different and the default would always be a valid config node that already exists. Is this not the case? How do I change it? The problem here is that I have to select a config node, close the child, and then reopen it to see the data that it is fed from the config node. Is there anyway to fix this?
As far as I know, a node (which uses a config node) defaults to 'none', and you need to click the '+' to create a new config and associate it to the node. This makes sense (at least to me).
If there is a use-case for a default, auto-created/auto-assigned config node, I believe it needs to be implemented by you in your node configuration code.
If there is already a config (of the correct type) (i.e. one or more already exist) why doesn't the config dropdown default to the first available config node?
I am 95% certain the config selector used to automatically pick up the first config available (in the days before the [Add] and [Edit] buttons were separated out)
Yes, Steve-Mci is correct, I'm only asking about the dropdown's default value when a valid config node already exists for the collection (created manually or otherwise)
