2 Correct answers
You could run both the scripts in the same engine, something like
#targetengine "main"
The you can set the variable you want to pass as a global variable and that will be available to script B.
Another approach could be to use the doScript method to call script B instead of #include. This method takes an array as an argument to pass to the calling script
-Manan
Disregard, I just ran a test and if I call Script_B from Script_A using the include statement, all of the Scrpt_A variables and values are available to Script_B, so I don't need to pass it a variable.
33
Replies
Hi @Marshall_Brooks , I'm not sure if this helps—ignore if it doesn’t. The #include file could have any number of public functions, constants, and variables, which may or may not be run from your script.
So this MyLibrary.jsxinc example has 2 public functions:
/**
* Simple PDF Prest dialog
* @ return the chosen dialog
*/
function exportPDFDialog(){
var pp;
var theDialog = app.dialogs.add({name:"Choose a Preset", canCancel:true});
with(theDialog.dialogColumns.add()){
pp = dropdowns.add({stringList:app.pdfExportPresets.everyItem().name, selectedIndex:3, minWidth:80});
}
if(theDialog.show() == true){
pp = app.pdfExportPresets.item(pp.selectedIndex);
theDialog.destroy();
return pp;
}
}
/**
* Makes a new named Layer
* @ param the document to add the layer to
* @ param new layer name
* @ return the new layer
*/
function makeLayer(d, n){
if (d.layers.itemByName(n).isValid) {
return d.layers.itemByName(n);
} else {
return d.layers.add({name:n});
}
}
/**
* A read only constant
*/
const MAGIC_NUMBER = 1.045;
/**
* A read write variable
*/
var vNum = 5
I can include and run them from a jsx file including a dialog function which returns the results:
#include "MyLibrary.jsxinc";
//run the exportPDFDialog() function from MyLibrary.jsxinc
alert("Chosen Export Preset: " + exportPDFDialog().name)
//run the makeLayer() function from MyLibrary.jsxinc
var ns = makeLayer(app.activeDocument, "MyNewLayer");
alert("New Layer Named: " + ns.name);
On run:
@Marshall_Brooks I'm sorry to say that you are creating a horrible architecture. I strongly suggest you put your overall control code into the main script and include (at the start of the script—not using predicate logic) just library functions and objects.
As for the stack overrun, have a look in the debugger and see which function is filling the stack. For example I created a stack overrun by making a function call another function which then called the other function back...
- Mark
AdChoices