Hi together,
I have taken time to understand the Shortcut principle.
Now I’m quite sure, I had understood the principles right, while writing the Topic.
But there are restrictions, those make it difficult or impossible to do the desired job.
###1. Problem
Currently, everytime I write something in the Target field and «Apply» it, the Target mode «Parent node» seams to be deleted/deselected…
####But why there is this Target-field, if it is not contemplated to combine the inserted Target-value with the selected “target mode”?
####Is this a bug, or is there a possibility to overwrite this limitation, so I could use the «Target»-field additional to the selected Target mode «Parent node»?
###2. Problem
It seems, the Target mode «Selected target» allow only databased known target’s as its own. So I could not even choose an hard-coded link like “/parentNodeName.html#desiredIdPosition”
####Is there a possibility to overwrite at least this limitation, so I could use the «Target»-field to set a hardcoded link with ID-anchor?
Of course, a additional solution with «Parent Node» or «First child node» would make a lot more sense. So in future, changing «URL path segment» values, would not end up in error messages for Editor’s who do not know the relationships…
####Would be great to find a helping mind for kill this limitation, or to find a work-around! Or do I have to do a Bug-Report or push an PR for this?
But maybe this is not a bug. Only the shortcut-principle is not flexible enough and the field «Target» is missing a DependingProperty-solution? (wich is quite difficult to understand from the references – I know : Elements in inspector show/hide –> by conditional value of other Element).
And maybe I misunderstood something in the shortcut-principle?
Would be great to hear something about. Thanks!