#5352 closed defect (invalid)
OMEdit allows editing of models despite "Activate Access Annotations" enabled
| Reported by: | Dietmar Winkler | Owned by: | Adeel Asghar |
|---|---|---|---|
| Priority: | high | Milestone: | 1.14.0 |
| Component: | OMEdit | Version: | |
| Keywords: | Cc: |
Description
I tested the support in OMEdit for Access Annotations and there seems the be a bug which still allows for changing parts of the model.
I tested this on an exported development version of OpenIPSL (file attached) and demonstrated it in a small video (attached.
Attachments (2)
Change History (5)
by , 6 years ago
| Attachment: | OpenIPSL.mo added |
|---|
by , 6 years ago
| Attachment: | 2019-02-21 11:03:04.277646.mkv added |
|---|
comment:1 by , 6 years ago
| Milestone: | Future → 1.14.0 |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
follow-up: 3 comment:2 by , 6 years ago
I agree the ticket is invalid with respect to the read-only. I understand now what the meaning there is.
However the CPU load is occurring when I move as in graphical move on the diagram layer not as in moving classes within the library. This is not something that is acceptable.
comment:3 by , 6 years ago
Replying to dietmarw:
I agree the ticket is invalid with respect to the read-only. I understand now what the meaning there is.
However the CPU load is occurring when I move as in graphical move on the diagram layer not as in moving classes within the library. This is not something that is acceptable.
Yes I know. You will actually get very good results if you save the library in directories structure.
Well the setting
Activate Access Annotationsis just an option to switch on/off the access protection annotations. It has nothing to do with making the model read-only or non-editable.In your example the components whose handlers are dark red are the inherited components. The tooltip can tell you the base class.
The CPU usage issue is valid but there is nothing I can do right now. The problem is that the library is saved in one file and when you move a component we need to adjust the text of all the classes in the library. That takes a bit of with the current frontend and API we have. Maybe this will improve when we move to the new API and frontend.