Replies: 7 comments
-
Hi, the dirty state handling is GLSP has been updated recently (eclipse-glsp/glsp-server#32). Unfortunately the ecore-glsp project is currently still using the old GLSP plugins (we recently moved to Eclipse) so you cannot consume this update (yet). I think @camille-letavernier is handling the Eclipse-migration. Once this is done you can change the dirtystate from the server side with a |
Beta Was this translation helpful? Give feedback.
-
[simongraband] I am currently working on updating the dirty Indicator, however i am unsure on what the best way, to update the indicator, is. I had a look at the PR, and it looks to me as i only need to update the |
Beta Was this translation helpful? Give feedback.
-
Hi, there is no need to update the isDirty() method directly. In theory the dirty state managment works out of the box with GLSP. Currently this is not the case for ecore glsp because you use customized action handlers that are missing some features. |
Beta Was this translation helpful? Give feedback.
-
In particular im talking about |
Beta Was this translation helpful? Give feedback.
-
On modelSave the modelState.saveIsDone() method has to be executed and a |
Beta Was this translation helpful? Give feedback.
-
In addition, the handlers for operationAction and undoRedo have to return a |
Beta Was this translation helpful? Give feedback.
-
Currently the Editor does not recognize moving Edges as Changes to the file and does not update the dirty Indicator next to the filename.
My question would be where this indicator is set, so i can update that?
original thread by simongraband
Beta Was this translation helpful? Give feedback.
All reactions