Skip to content

base ODD behaviour: dependend ODDs are not rebuilding after a change in their base ODD #238

@flicksolutions

Description

@flicksolutions

The visual ODD editor has a feature where you can define a base ODD.

Current behaviour:
The value in the base ODD field is not persistent. It is lost upon reload. This means upon editing an ODD, base styles are lost if one forgets to reset the base styles. What's worse: If ODD A is a base ODD of ODD B and ODD A is edited, ODD B will not change. One has to open ODD B, set ODD A as a base ODD again, and save it again for changes to be propagated. This makes the whole workflow extraordinarily tedious and error-prone.

Expected behaviour:
The base ODD is a persistent field. If an ODD is edited, it is checked whether any other ODDs depend on it. Dependend ODDs are recalculated.

Thanks for your feedback

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions