Opening a file in InDesign from jsx

Question

This seems trivial, but I can't seem to get InDesign to open a file.

I'm can pass a file path to the index.jsx using an evalScript:

// pasteFile is '/Users/me/Desktop/Blah/05_21_2018_PRODUCT/Blah_05_21_2018_PRODUCT.indd'
//csInterface.evalScript("openFile('" + JSON.stringify(pasteFile) + "')");
    csInterface.evalScript("openFile('" + pasteFile + "')");

Then in the .jsx, I simply try to open it:

#include "json2.js"
function openFile(someFile) {
     //var aFile = JSON.parse(someFile);
     alert(someFile);
     var docRef = app.open(someFile);
}

I read elsewhere that you need to JSON.stringify then JSON.parse an argument being passed to the jsx. Regardless, alert(someFile); works in both cases, and it alerts with the proper file path. app.open(someFile); appears to do nothing, however.

Any ideas?

toddm72 · Accepted Answer

I double checked that InDesign CC is updated, and that the file I'm opening is for the correct version.

I have a hunch, though I haven't been able to prove it yet.

The script is copying a file to a new folder, then trying to open that file. I'm using node's fs to do the copying. Perhaps it's trying to open the file before the pipe finishes?

Here's what it's doing:

   // node
    var fs = require('fs');
    fs.createReadStream(copyFile).pipe(fs.createWriteStream(pasteFile));
    
    csInterface.evalScript("openFile('" + pasteFile + "')");

I'm newish to JavaScript and even newer to node, so I'm still trying to work out a way to force the script to wait for the createWriteStream to finish before running the evalScript.

If that even is the issue...

I worked it out, my hunch was right.

It was trying to open the file before the createWriteStream finished.

Changed that code to:

    // node
    var fs = require('fs');
    var ws = fs.createWriteStream(pasteFile);
    fs.createReadStream(copyFile).pipe(ws);
    
    ws.on('finish', function(){
        csInterface.evalScript("openFile('" + pasteFile + "')");
    });

This waits for the stream to 'finish', then runs the evalScript. Working now.

Loic.Aigon · Answer

That's a peculiarity of ExtendScript and I find it reliable enough. However, the FileSystem Class of CEP has some advantages like checking right managements which ExtendScript can't. And node has probably some interests if you do pipe operations and monitor async processes. But for minor operations, I am ok with ExtendScript File class.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded