What triggers scriptlet execution?

[MichPaule]

EA 16.1.1629 (64bit) .QEAX database
Situation:
A diagram with elements containing scriptlets is open but hidden behind another active diagram.
Elements shown in the active diagram are modified using scripting.

Observation:
The scriptlets from the currently hidden diagram are executed and the message "Running scriptlets" pops up for every element.
If the diagram has been closed before running the script then no scriptlets are being executed (obviously).

Questions:
Why are the scriptlets being executed on this hidden diagram?
Which actions in a script trigger scriptlets execution?

Thanks in advance for any hints!

[Elpis]

I'm not sure what do you mean by diagram being *hidden"...
AFAIK scriplets are launched on the diagram being open or reloaded.

[MichPaule]

I'm not sure what do you mean by diagram being *hidden"...

The diagram is opened but in the background. Another diagram hides it.

AFAIK scriplets are launched on the diagram being open or reloaded.

The diagram containing the scriptlets has been opened some time ago and it is not reloaded at this time.
It is just sitting in the background.

So the question remains: Which action triggers the scriptlets of this diagram?

[MichPaule]

So the question remains: Which action triggers the scriptlets of this diagram?

After quite a long time I had the chance to dig deeper.
Outcome:

• Repository.RefreshModelView(pkdId)
• Repository.AdviseElementChange(eleId)

trigger execution of all scriptlets from all open diagrams.
Regardless whether pkdId or eleId are related to the diagram content or not! 

To me it seems like a bug!

[Geert Bellekens]

So the question remains: Which action triggers the scriptlets of this diagram?

After quite a long time I had the chance to dig deeper.
Outcome:

• Repository.RefreshModelView(pkdId)
• Repository.AdviseElementChange(eleId)

trigger execution of all scriptlets from all open diagrams.
Regardless whether pkdId or eleId are related to the diagram content or not! 

To me it seems like a bug!

In most cases you can replace RefreshModelView with ReloadPackage.
This is often a lot less annoying, since it doesn't reload all diagrams.

Geert

[MichPaule]

In most cases you can replace RefreshModelView with ReloadPackage.
This is often a lot less annoying, since it doesn't reload all diagrams.

Thanks Geert,
in fact I did this during bugfixing.
But sometimes it is essential to also update the opened diagrams impacted by the change.

The point is: RefreshModelView(pkgId) also triggers the scriptlets execution of diagrams otherwise completely unrelated to the change in package pkgId.