Restart the extension on its closing

Hi all

I'm doing a plug-in for InDesign that I need that he should continue to run after the user closes the Panel.

My understanding of the structure of the extension is that it has 4 main parts (only not including plugins)

(1) the main engine of the CEP

(2) the manifest.xml

(3) the HTML and JS engines

(4) the jsx engine.

When closing the HTML Panel, associated JS files will stop working, a "com.adobe.csxs.events.WindowVisibilityChanged" event will be fired at the CEP 6.1 but the JS engine will have already launched the bucket before it can receive event RIP.

The main engine of the CEP and his faithful friend the manifest.xml is still alive and well, but the manifest.xml does not recognize the event 'com.adobe.csxs.events.WindowVisibilityChanged' so that cannot be used in the < started > tag.

Our poor orphans jsx engine seems totally unaware of the tragedy which became it and continues to send messages to the JS engine deceased who are normally redirected to the sewer.

The engine of the CEP will pick up messages so if the manifest.xml < started > tag includes certain events such as documentAfterActivate which can trigger the JS engine to get a life, but it doesn't seem to be a way of sending the jsx engine or receive on the fine VINE of the custom events that will revive the JS engine.

If I could relive the JS engine on a beforeSave event that would be good enough for me.

In desperation, I might have an idle task, which would be called the prototype of requestOpenExtension but I don't think only that the cans will be the engine of jsx (please, correct me if I'm wrong).

In short how can I get the extension to continue to operate after that his group is close?

An important note is that after the Committee has be closed once and then restarted, it will continue to function even after the closure of the Panel.


How can I do that also after the first closure of the extension Panel should continue to operate as it does after the closures?

The life cycle of the product is:

<Lifecycle>
    <AutoVisible>false</AutoVisible>
    <StartOn>
        <Event>applicationActivate</Event>
        <Event>documentAfterActivate</Event>
        <Event>documentAfterSave</Event>
    </StartOn>
</Lifecycle>

TIA

Trevor

Trevor

How to do an "Invisible HTML Extension" - to hold your code JSX - which must persist and a Panel for the user interface bits separate extension?

I hasten to add that I have never ever fact - but it seems that this could work. I've only read "Invisible HTML Extensions" in the cookbook CEP 6.1 Extension

FWIW

Pete

Tags: Adobe

Similar Questions

Maybe you are looking for