2 results found

1. [ID-4260022][ExtendScript] Folder.prototype.create fails on macOS/InDesign 20.1

   Something has broken in ExtendScript's Folder.prototype.create method on MacOS and Indesign 20.1.

   To test yourself, save the following script to your disk, and run it in Indesign.

   
   (function () {
   
       var scriptFolder = File($.fileName).parent;
       var deepFolder = Folder(scriptFolder + '/A/B/C/D');
   
       if (!deepFolder.exists)
           deepFolder.create();
   
       if (deepFolder.exists) {
           alert('Folder created successfully.');
       }
       else {
           alert('Failed to create folder "' + deepFolder.fsName + '".');
       }
   
   })();
   
   

   Expected Result:
   Prior to this bug, this script would successfully create the folder and subfolders, in the same folder as the script is saved.

   Actual Result:
   Each time the script is run, it creates only one more level of sub folder. So the first time run it creates folder "A", then the next time run it creates "B" etc.

   See also this thread on the forum.

   Something has broken in ExtendScript's Folder.prototype.create method on MacOS and Indesign 20.1.

   To test yourself, save the following script to your disk, and run it in Indesign.

   
   (function () {
   
       var scriptFolder = File($.fileName).parent;
       var deepFolder = Folder(scriptFolder + '/A/B/C/D');
   
       if (!deepFolder.exists)
           deepFolder.create();
   
       if (deepFolder.exists) {
           alert('Folder created successfully.');
       }
       else {
           alert('Failed to create folder "' + deepFolder.fsName + '".');
       }
   
   })();
   
   

   Expected Result:
   Prior to this bug, this script would successfully create the folder and subfolders, in the same folder as the script is saved.

   Actual Result:
   Each time the script is run, it creates only one more… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   FIXED  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

   Fix for this issue is available in the latest InDesign Release version 20.2, available via Adobe CCD app.

   
   

   --

   Adobe InDesign team

2. Navigation Points Not Available to Scripting in InDesign 2021 (16.0)

   Problem Description:
   Querying navigation points inside a movie trigger errors from InDesign 16.

   Steps to Reproduce:
   1. Query movie.navigationPoints.length or movie.navigationPoints.count() with Extendscript.

   The following script shows this issue(s) with simple document containing a move and one button with a play at navigation point action applied.

   var btn = app.activeDocument.buttons[0];
   var beh = btn.behaviors[0];
   var mov = beh.movieItem;
   var navPts = mov.navigationPoints;
   try{
   alert(navPts.length); /doesn't exist/
   }catch(err) { alert([err,err.line])}

   try{
   alert(navPts.count()); /*Give incorrect error - Error: Request failed because the underlying functionality is no longer available in the current version of the application */
   }catch(err) { alert([err,err.line])}

   alert(navPts.everyItem().getElements().length); /incorrectly says zero, when there are 2 navigation points/

   Actual Result:
   Each produces two separate errors.

   Expected Result::
   Both should be valid queries.

   Any Workarounds:

   No. Expected functionality is simply missing.

   movie.navigationPoints.everyItem().getElements().length at least doesn't produce an error, but it also doesn't include navigation points.

   This feature was added back to InDesign, but the scripting of it was neglected. I've filed a bug in prerelease as well. Posting here so others are aware.

   Problem Description:
   Querying navigation points inside a movie trigger errors from InDesign 16.

   Steps to Reproduce:
   1. Query movie.navigationPoints.length or movie.navigationPoints.count() with Extendscript.

   The following script shows this issue(s) with simple document containing a move and one button with a play at navigation point action applied.

   var btn = app.activeDocument.buttons[0];
   var beh = btn.behaviors[0];
   var mov = beh.movieItem;
   var navPts = mov.navigationPoints;
   try{
   alert(navPts.length); /doesn't exist/
   }catch(err) { alert([err,err.line])}

   try{
   alert(navPts.count()); /*Give incorrect error - Error: Request failed because the underlying functionality is no longer available in the current version of the application */
   }catch(err) { alert([err,err.line])}

   alert(navPts.everyItem().getElements().length);… more

   64 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   6 comments  ·  Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   FIXED  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

   The fix for this issue is available in the latest InDesign release 16.2.1
   Please update to this latest version to get the fix.

   —
   Adobe InDesign team