Ticket #576 (closed Defect: fixed)
Core: the Directives sent back to the Webclient are not complete in every situation
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.1.3 |
Component: | DeepaMehta Standard Distribution | Version: | 4.1.2 |
Keywords: | Cc: | dgf, Malte, JuergeN | |
Complexity: | 3 | Area: | Application Framework / API |
Module: | deepamehta-core |
Description
This creates situations where the view is not in-sync with the DB.
Problematic situations comprise:
- When changing the "Include in Label" setting in a type form while the respective association definition is visible on the canvas, the association label on the canvas is not updated (#564).
- When changing a type's data type in a type form while the former data type and the association is visible on the canvas, the association does not disappear (although it does not exist anymore). Clicking it throws a server-side error.
Change History
comment:2 Changed 11 years ago by Jörg Richter
Core: sync view on Include in Label change (#564).
When changing the "Include in Label" setting in a type form while the respective association definition is visible on the canvas, the association label on the canvas is updated.
CHANGES
When calling a CompositeValue manipulator method (set(), setRef(), remove()) the passed set of Directives is extended by a UPDATE_TOPIC resp. UPDATE_ASSOCIATION directive.
BREAKING CHANGES
Core API Type interface
- setLabelConfig() has a directives parameter
comment:3 Changed 11 years ago by Jörg Richter
- Status changed from accepted to closed
- Resolution set to fixed
Core: sync view on data type change (#576).
When changing a type's data type in a type form while the former data type and the association are visible on the canvas, the association disappears. It does not exist anymore.
BREAKING CHANGES
Core API Type interface:
- setDataTypeUri() has a directives parameter
Close #576