Hi community,
I seem to have a timing problem and don't know how to solve it.
The following procedure:
- An Indesign file and the corresponding JSON arrive in the input folder(Folder2).
- Job is kept short, come together.
- It is passed to Indesign and the Indesign file is opened.
It is opened with the AdobeExtended script 'DGN-Automatisierung-Proxy.jsx' and the UXP script is to be executed(after).
- The script states that the UXP should be executed (because the switch does not support UXP).
The problem is that I get the error message (from the script) that no Indesign document is open(?).
So the Indesign file is passed to the Indesign app, the app opens and closes the document before(!) the script is executed. And when the script wants to execute its function, the ID document is already closed again.
How can I work around this, where is the error?
Thanks for help
Time problem on handover - No document opened
Re: Time problem on handover - No document opened
If an Indesign file and a JSON file arrive in a folder preceding the Indesign app, they will be processed by the app as 2 individual files and certainly for the JSON that will not work well. Or is it a package (which is a folder) with the JSON file inside? Is the non-UXP script used in the Open or Command property? If it is in the Open property then the script has to start by creating an empty file and making sure that something happens. If it is in the Command property the file will be open and available as $doc. How are you calling the UXP script from the non-UXP script? According to the Indesign API it should be something like
What is it you are doing in the UXP script that cannot be done using the regular Indesign API?
Code: Select all
app.doScript(new File("path to the script"), ScriptLanguage.UXPSCRIPT, ["parameter1","parameter2"]); //not tested!
What is it you are doing in the UXP script that cannot be done using the regular Indesign API?
Re: Time problem on handover - No document opened
Hi,
we are already successfully using UXP locally and would have expected this to also happen in the environment with Switch.
But we had to realize that Switch cannot work with it and therefore the 'little push' by the ExtendScript.
With the UXP, placeholders are to be exchanged and text replacements/adjustments are to be created.
Thanks for the tip, we'll take a look.
we are already successfully using UXP locally and would have expected this to also happen in the environment with Switch.
But we had to realize that Switch cannot work with it and therefore the 'little push' by the ExtendScript.
With the UXP, placeholders are to be exchanged and text replacements/adjustments are to be created.
Thanks for the tip, we'll take a look.