`elements.changed` event handler doesn't return an actual information about BPMN schema about bpmn-js HOT 4 CLOSED

@corocoto Please share with us a screen capture that provides additional context. If you seek to get an elements.changed event during direct editing (cf. below), then you'll see that this is not the case. It only commits on unfocus, ENTER or another user action.

from bpmn-js.

@corocoto Label editing, unless commited is ephemeral. Hence it never reaches the underlying model, and no elements.changed is called.

If you build upon the change to happen please raise an issue and clearly lay out your use case.

from bpmn-js.

@nikku, yeah, I suppose your screencast with shown scenario fully covers my case. Thanks!

But I have a small counter question. The scenario shown below will also not trigger the elements.changed event? (node's label creation process)

And if it is, I would like to understand why the event didn't dispatch. I mean, I want to understand why it works so. Because for me, any manipulation with an element (including text editing) - is also refer to an element editing.

from bpmn-js.

@nikku, I see. Thanks a lot for description of working process! It's really useful information that should to know.

from bpmn-js.