major
nice-to-have
minor
#25217
Layout-Export führt zu invaliden Komponenten-Referenzen bei Referenzierung einer bestehenden Komponente
#25327
Modell-Editor: Falsche Kompositionsmarker, wenn Container-Typ in Diagramm von Content-Typ gezogen wird
defect
minor
#25628
Aktualisierung der TreeGrid bei ModelCreateEvents kompliziert zu konfigurieren
Suppose there is a tree and a TreeGrid, both of which display the demo data. In that case, the components behave differently if the demo data is expanded, potentially requiring the displayed tree to be partially updated.
- In the Grid, a new row is added only if the model for that list element matches the component’s model. The model of the list element is calculated by ` retrieveModelForListElement ` of the corresponding `GridBuilder` and is configured for in-app grids. For complex TreeGrids, this can become very complicated and confusing.
- The `tl:TreeComponent`, on the other hand, considers the parents of the newly created objects. For each parent node contained in the tree and displayed, the subtree is updated.
In the case of a tree, a grid should behave similarly to the `TreeComponent` and perform updates based on the parent structure. For `TableGrids`, the existing functionality can continue to be used.
Test
No test. Refactoring.