I want to, after a model has been loaded in the modeler, lock the modeler from user changes (disable user modeling), and also being able to unlock (re-enable user modeling).
In effect, that would be the equivalent to first using Modeler and then user Viewer, and Modeler again - but without having to import the XML every time I lock/unlock.
Disabling modeling actions can occur while having the context-pad and/or popup-menu activated (the menu should be re-rendered or disappear).
My three alternatives I’ve come up
- Swapping Modeler with Viewer (not preferred)
- Unloading/loading modeling modules, i.e. “destroy” but for specific modules only
- Modeling modules can be disabled by a flag/event
I would be happy to provide a PR with any code required to support my use case, but I would appreciate advise on the design and how to best fit the bpmn-js/diagram-js architecture.