My impression is that if a script
- uses KMEngine.doScript to call a macro, and
- subsequently reads KMEngine.Variables() to inspect the value of variables updated by the called macro
then the values retrieved are out of date (the unmodified values which they had when the calling script was launched).
If this is right, is there any way for the calling script to get access to new variables states which result from the .doScript call ?
( Context: the experimental progress bar plugin uses a series of .doScript() calls, and I wondered whether the calling applet could inspect their effects, update a returnValue variable accordingly, leaving that returnValueβs new state legible to the shell script which calls the applet : - )
( Matrushka doll territory here β the applet has to be called by a shell script (rather than directly by the plugin mechanism) to allow for the display of a notification dialog )
Shell called by plugin β Applet β .doScript mutations of variables