Open gerberm-at-msg opened 1 month ago
Hello @gerberm-at-msg,
thank you for the bug report and the suggestion. We will try to fix the bug ASAP and discuss resolving references in place. This feature would probably introduce some challenges. When just a property is referenced I see no issues but how should references to an entire Submodel or an AAS be handled?
Great thank you.
This feature would probably introduce some challenges. When just a property is referenced I see no issues but how should references to an entire Submodel or an AAS be handled?
I think in a perfect world they would be "inserted" as they are part and not referenced. To keep track, they could have a label with the reference. This would be a great step towards aggregation of DT. It would be probably a subsequent / recursive request.
That's an interesting idea. So you mean that I can basically unfold the reference element like a Submodel or collection and navigate deeper down from there. That could work but nevertheless it would be a challenging task.
I will add this to our backlog.
Is your feature request related to a problem? Please describe. When referencing to attributes, a "jump" button is displayed, to jump to the referenced attribute.
Describe the solution you'd like For making the UI more user friendly, it would be nice if referenced values / attributes are directly displayed. P.s. the Jump button is broken in the "AAS Viewer"-Mode, but works fine in "AAS Editor"
Example