[x] I have verified that I am running the latest version of the COMET-IME
[ ] I have searched open and closed issues to ensure it has not already been reported
Description
in some limited testing, the property grid (available from the View-tab) seems to be sufficiently reactive to changes to the model made in the IME browsers (e.g. changes in element definitions browser).
The other way around however, some fields that are editable in the property-grid are not immediately reflected in the element definitions browser, see examples below from testing.
Since the effects in any case are real changes to the model, for me it should either be reflected in the browser(s) immediately, or the property grid should maybe not be editable. With the current implementation, it may become unclear, and there is a definite risk of unintended and unnoticed changes
the field "Is OptionDependent"
this can be toggled, where the change is only reflected in the browser on closing and reopening
the field "ToBePublished"
sets it ready for publication, but again only visible in publication browser on closing and reopening
Steps to Reproduce
open publication browser, element definition browser, and the property grid.
then select a parameter from the model to inspect and edit:
the field "Is OptionDependent"
this can be toggled, where the change is only reflected in the browser on closing and reopening
the field "ToBePublished"
sets it ready for publication, but again only visible in publication browser on closing and reopening
Logs
[x] There are no logs regarding the issue
{ ] I have attached a log file or included the relevant section in this issue
System Configuration
COMET version:
[ ] COMET-IME:
[ ] Other:
Web Services:
[ ] CDP4/COMET Web Services version:
[ ] OCDT WSP version:
Environment (Operating system, version and so on):
Prerequisites
Description
in some limited testing, the property grid (available from the View-tab) seems to be sufficiently reactive to changes to the model made in the IME browsers (e.g. changes in element definitions browser).
The other way around however, some fields that are editable in the property-grid are not immediately reflected in the element definitions browser, see examples below from testing.
Since the effects in any case are real changes to the model, for me it should either be reflected in the browser(s) immediately, or the property grid should maybe not be editable. With the current implementation, it may become unclear, and there is a definite risk of unintended and unnoticed changes
the field "Is OptionDependent" this can be toggled, where the change is only reflected in the browser on closing and reopening
the field "ToBePublished" sets it ready for publication, but again only visible in publication browser on closing and reopening
Steps to Reproduce
open publication browser, element definition browser, and the property grid. then select a parameter from the model to inspect and edit:
the field "Is OptionDependent" this can be toggled, where the change is only reflected in the browser on closing and reopening
the field "ToBePublished" sets it ready for publication, but again only visible in publication browser on closing and reopening
Logs
System Configuration