64 results found

1. Unable to copy/past script label text

   With this post I would like to report another bug.

   In Indesign CC2026, it's not possible to copy/past a script label text.

   Please fix this.

   I'm using Os X.

   1 vote

   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

   0 comments  ·  Scripting  ·  Edit…  ·  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

2. [ID-4274715] Missing anchoredObjectSettings for FlexObject in DOM

   The anchoredObjectSettings for FlexObject is missing in DOM.
   So it’s impossible to manipulate the anchor properties of a Flex Layout inside a text frame.

   Please, fix it and expose the anchoredObjectSettings of a flex layout object.

   3 votes

   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

   Under Review  ·  0 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

3. Find/Change saved queries lose numeric precision for indent values

   Version:
   Adobe InDesign 21.0.2
   macOS 26.2
   Issue also observed in much earlier versions (since CS5.5).
   Steps to reproduce:
   Create a document with paragraph units set to millimeters.
   Create a paragraph with a left indent of exactly 5 mm.
   Open Find/Change.
   In Find Text, set Left Indent to 5 mm by typing it manually.
   Run Find – the paragraph is found.
   Save this Find/Change query.
   Reload the saved query.
   Run Find again.
   Expected result:
   The saved query should find the same paragraphs as when the value is entered manually.
   Actual result:
   After reloading the saved query, the paragraph is not found.
   Additional details:
   Via the scripting API the difference can be observed.
   Manual entry via UI:
   app.findTextPreferences.leftIndent = 14.1732283464567
   After reloading saved query:
   app.findTextPreferences.leftIndent = 14.17322834
   The reduced numeric precision causes the query to fail.
   This appears to be a precision loss when persisting Find/Change query settings.
   The issue affects both UI and scripting workflows.
   Using paragraph or character styles does not prevent this issue, as it is related to how numeric values are stored and restored in saved queries.

   Version:
   Adobe InDesign 21.0.2
   macOS 26.2
   Issue also observed in much earlier versions (since CS5.5).
   Steps to reproduce:
   Create a document with paragraph units set to millimeters.
   Create a paragraph with a left indent of exactly 5 mm.
   Open Find/Change.
   In Find Text, set Left Indent to 5 mm by typing it manually.
   Run Find – the paragraph is found.
   Save this Find/Change query.
   Reload the saved query.
   Run Find again.
   Expected result:
   The saved query should find the same paragraphs as when the value is entered manually.
   Actual result:
   After reloading the saved query, the paragraph is not found.… more

   4 votes

   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

4. [ID-4273762] Critical bug — Dropdown / <select> / sp-picker not working in UXP plugin under InDesign 2025 (Win & Mac)

   I'm contacting you about a recurring bug I've encountered—and that several other developers have reported—since the Adobe InDesign 2025 update (versions 20.4, 20.4.1, 20.5).

   🔹 Problem Description

   • In a plugin using Adobe UXP (UI HTML or Spectrum), the dropdown elements <select>—or <sp-picker>—no longer respond to clicks: the border may change color, but the list doesn't open, and it's impossible to select an item.

   • Even when using minimal HTML code or testing from UXP Developer Tools (Playground), the problem persists.

   • This bug seems to affect several environments (Windows 11, different versions of InDesign, and possibly macOS as well, according to community feedback).

   • In some cases, events (click, change, keydown, etc.) are no longer emitted for form controls.
     Adobe Creative Cloud Developer Forums

   🔹 Impact

   Existing plugins become unusable — users are unable to enter or select options, thus blocking normal operation.

   Production usage is severely disrupted.

   Loss of confidence in the stability of the UXP runtime.

   🔹 Step to reproduce

   1 - Create starter package
   2 - Add select with options tags
   3 - Use UXP Developer tools or package it
   4 - Open panel in Indesign 2025
   - under 20.4 version, it works fine. We can open option in select
   - upper 20.3 version, select tags, checkbox,... doesn't work

   🔹 What I'm asking

   Can you confirm that this bug has been identified internally?

   Is there a planned fix (future version or update) to restore the behavior of dropdown lists/sp-picker/select in UXP under InDesign 2025?

   If not, is it possible to obtain an official workaround (patch, beta build, directive) for our plugins in production?

   Thank you in advance for your help—this bug seriously compromises the reliability of UXP plugins. I am available to provide code examples, reproductions, or logs if that would be helpful.

   Sincerely,
   Stéphane Senocq

   I'm contacting you about a recurring bug I've encountered—and that several other developers have reported—since the Adobe InDesign 2025 update (versions 20.4, 20.4.1, 20.5).

   🔹 Problem Description

   • In a plugin using Adobe UXP (UI HTML or Spectrum), the dropdown elements <select>—or <sp-picker>—no longer respond to clicks: the border may change color, but the list doesn't open, and it's impossible to select an item.

   • Even when using minimal HTML code or testing from UXP Developer Tools (Playground), the problem persists.

   • This bug seems to affect several environments (Windows 11, different versions of InDesign, and possibly macOS as well, according… more

   •  

   1 vote

   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

   Under Review  ·  4 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

5. Error Number: 30619

   When opening InDesign GA 21.0 I am now getting this pop message. I do not get the same thing in Beta version

   •  

   1 vote

   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
   Resolved For User  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   Hi,

   As confirmed by the user, the issue is resolved by removing second scrollframe folder

   —

   Adobe InDesign Team

6. [ExtendScript] app.languagesWithVendors.itemByName fails.

   Adobe Indesign 20.5 on MacOS 15.6.1

   To reproduce:

   1. run the following script:

   (function () {
   
       var targetLanguageName = 'Dutch: 2005 Reform';
   
       // try to get the language the normal way
       var targetLanguage = app.languagesWithVendors.itemByName(targetLanguageName);
   
       if (!targetLanguage.isValid)
           alert('Language "' + targetLanguageName + '" is invalid when accessed via `itemByName`.');
       else
           return;
   
       // now loop over the languages checking the name each time
       for (var i = 0; i < app.languagesWithVendors.length; i++)
           if (app.languagesWithVendors[i].name === targetLanguageName)
               targetLanguage = app.languagesWithVendors[i];
   
       if (targetLanguage.isValid)
           alert('Language "' + targetLanguageName + '" is valid when accessed by index.');
   
   })();
   

   1. Expected result: that app.languagesWithVendors.itemByName returns a valid language for "Dutch: 2005 Reform" and the script exits quietly.

   2. It returns an invalid object. But note that we can get the valid language directly by looping over each language.

   See also this forum thread.

   Adobe Indesign 20.5 on MacOS 15.6.1

   To reproduce:

   1. run the following script:

   (function () {
   
       var targetLanguageName = 'Dutch: 2005 Reform';
   
       // try to get the language the normal way
       var targetLanguage = app.languagesWithVendors.itemByName(targetLanguageName);
   
       if (!targetLanguage.isValid)
           alert('Language "' + targetLanguageName + '" is invalid when accessed via `itemByName`.');
       else
           return;
   
       // now loop over the languages checking the name each time
       for (var i = 0; i < app.languagesWithVendors.length; i++)
           if (app.languagesWithVendors[i].name === targetLanguageName)
               targetLanguage = app.languagesWithVendors[i];
   
       if (targetLanguage.isValid)
           alert('Language "' + targetLanguageName + '" is valid when accessed by index.');
   
   })();
   

   1. Expected result: that app.languagesWithVendors.itemByName returns a valid language… more

   2 votes

   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

   2 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

7. Title: `afterSelectionChanged` triggers "The object no longer exists" error even when a valid object is selected Description: When using th

   Title:
   afterSelectionChanged triggers "The object no longer exists" error even when a valid object is selected

   Description:
   When using the method addEventListener("afterSelectionChanged", ...) in an ExtendScript script for InDesign, the application consistently throws the following error:

   "The requested action could not be completed because the object no longer exists."

   This occurs even when:
   - A single TextFrame is manually selected,
   - The object is valid (isValid === true),
   - The code is wrapped in a try/catch,
   - An idleTask is used to defer execution.

   Steps to Reproduce:
   1. Open an InDesign document.
   2. Add the following script:

   function onSelectionChanged(event) {
   try {
   if (app.selection.length > 0 && app.selection[0].isValid) {
   alert("Selected: " + app.selection[0].constructor.name);
   }
   } catch (e) {
   alert("Error: " + e.message);
   }
   }

   app.addEventListener("afterSelectionChanged", onSelectionChanged);

   1. Select a TextFrame on the page.

   Expected Result:
   The script should display the type of the selected object without error.

   Actual Result:
   An error message appears immediately:
   "The requested action could not be completed because the object no longer exists."

   System Information:
   - InDesign Version: 20.4.1
   - OS: macOS 15.3.2
   - Language: French
   - Script executed from: Scripts Panel

   Comment:
   This behavior prevents reliable use of afterSelectionChanged for interacting with the selection. It appears that the event is triggered before the selection is fully stabilized, making app.selection[0] unusable.

   Title:
   afterSelectionChanged triggers "The object no longer exists" error even when a valid object is selected

   Description:
   When using the method addEventListener("afterSelectionChanged", ...) in an ExtendScript script for InDesign, the application consistently throws the following error:

   "The requested action could not be completed because the object no longer exists."

   This occurs even when:
   - A single TextFrame is manually selected,
   - The object is valid (isValid === true),
   - The code is wrapped in a try/catch,
   - An idleTask is used to defer execution.

   Steps to Reproduce:
   1. Open an InDesign document.
   2. Add the following script:

   … more

   1 vote

   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

   0 comments  ·  Scripting  ·  Edit…  ·  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

8. [ID-4265002][ExtendScript] Folder.execute() no longer works in Indesign 20.4

   Folder.execute() no longer reveals the folder and activate the Finder. It does nothing. Tested on Indesign 20.4 on MacOS 15.5.

   Steps to reproduce:

   1. Run this ExtendScript:

   
       Folder.desktop.execute();
   
   

   Expected result: activating the Finder, revealing the Desktop folder.

   Actual result: nothing.

   See also this post on the forum.

   •  

   •  

   32 votes

   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

   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
   Closed: Fixed  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   The fix of the issue is now available in the latest InDesign 2025(v20.4.1.004). We recommend you upgrade to the latest version for the fix.

   If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

   —

   Adobe InDesign Team

9. [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 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

10. Dropshadow > Size is limited to 0-144 points within scripting but you can enter higher numbers manually 0-1000 points

    My understanding is indesign dropshadow effect needs to be updated for the option: size within the dropshadow panel to be able to accept 0 - 1000 points for scripts. You can input higher numbers within the size by doing it manually but not with scripts for whatever reason. It will only accepts 0-144 point or 2 inches within the code.

    1. Indesign CC 2025
    2. Run the attached script a 100 in height image and you'll get the error.
    3. On the dropshadow applied to have the distance 5.0 in and size 5.0
    4. Distance: 5.0 in and Size: 0.0694 in
    5. Script attached.

    I have a script to automatically apply dropshadows and we have a formula where we take the height of the image and multiply that by 5% which gets placed in the Distance and Size. This works for smaller images but when there are larger images the number it puts into the distance works but the size seems to be limited to 2 inches. But if I do it manually it can go up to 13.8889″
    for the size

    I get this error: ERROR in applyDropShadow: Error: Invalid value for set property ‘size’. Expected Unit (0 - 144 points), but received “5.0 in”. 13.8889 in = 1000 points

    //@target "indesign"
    //@targetengine "session"

    function isValidObject(obj) {
    try {
    return obj && obj.isValid;
    } catch (e) {
    return false;
    }
    }

    function applyDropShadowByHeightInInches(obj) {
    if (!isValidObject(obj)) return;

    var doc = app.activeDocument;
    var originalH = doc.viewPreferences.horizontalMeasurementUnits;
    var originalV = doc.viewPreferences.verticalMeasurementUnits;
    
    try {
        // Switch the document to inches.
        doc.viewPreferences.horizontalMeasurementUnits = MeasurementUnits.INCHES;
        doc.viewPreferences.verticalMeasurementUnits   = MeasurementUnits.INCHES;
    
        // geometricBounds => [y1, x1, y2, x2] in INCHES now.
        var bounds = obj.geometricBounds; 
        var heightInches = Math.abs(bounds[2] - bounds[0]); // bottom - top
    
        // 5% of height in inches
        var dropShadowInches = heightInches * 0.05;
    
        // Apply the drop shadow
        var ds = obj.transparencySettings.dropShadowSettings;
        ds.mode     = ShadowMode.DROP;
        ds.angle    = 120;                 // Static angle
        ds.distance = dropShadowInches;    // in inches
        ds.size     = dropShadowInches;    // same as distance
        ds.opacity  = 35;                  // example opacity
        ds.noise    = 2.5;                 // example noise %
        ds.xOffset  = 0;
        ds.yOffset  = 0;
        ds.spread   = 0;
    
    } catch (e) {
        $.writeln("Error applying shadow: " + e);
    } finally {
        // Restore original measurement units
        doc.viewPreferences.horizontalMeasurementUnits = originalH;
        doc.viewPreferences.verticalMeasurementUnits   = originalV;
    }
    

    }

    function main() {
    if (app.documents.length === 0) {
    alert("No open documents.");
    return;
    }

    var doc = app.activeDocument;
    if (!isValidObject(doc)) {
        alert("Active document not valid.");
        return;
    }
    if (app.selection.length === 0) {
        alert("No objects selected.");
        return;
    }
    
    var count = 0;
    for (var i = 0; i < app.selection.length; i++) {
        var obj = app.selection[i];
        if (isValidObject(obj)) {
            applyDropShadowByHeightInInches(obj);
            count++;
        }
    }
    alert("Drop shadow applied to " + count + " object(s).");
    

    }

    main();

    My understanding is indesign dropshadow effect needs to be updated for the option: size within the dropshadow panel to be able to accept 0 - 1000 points for scripts. You can input higher numbers within the size by doing it manually but not with scripts for whatever reason. It will only accepts 0-144 point or 2 inches within the code.

    1. Indesign CC 2025
    2. Run the attached script a 100 in height image and you'll get the error.
    3. On the dropshadow applied to have the distance 5.0 in and size 5.0
    4. Distance: 5.0 in and Size: 0.0694 in
    5. Script attached.

    I… more

    •  

    •  

    1 vote

    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

    0 comments  ·  Scripting  ·  Edit…  ·  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

11. Multiple panel issues in the InDesign UXP plugin framework

    See description here:
    https://forums.creativeclouddeveloper.com/t/uxp-entrypoints-setup-loads-same-panel-always/8026

    6 votes

    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

    0 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

12. Websocket not connecting in windows

    In indesign 20.0.1, windows 11, manifest version 5. websocket never connects.

    https://forums.creativeclouddeveloper.com/t/windows-indesign-version-20-websocket-not-connecting/8528

    14 votes

    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

    2 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

13. do script bug in indesign 2025?

    I have a script (extend script) file that has worked flawlessly in every version of InDesign for the last 15 years or so. Bercause it is used in semi-automated workflow I trigger it from an AppleScript, using the "do script" command.

    InDesign 2025 suddenly incorrectly reports a syntax error "expecting ;"

    The javascript that gets called works as expected, without warnings when run from the script panel.

    This is highly problematic for me, since triggering the script from applescript is an essential part of my workflow.

    Adobe are welcome to contact me for more information

    1 vote

    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

    0 comments  ·  Scripting  ·  Edit…  ·  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

14. Applescript export and save commands not working

    InDesign 2025 - Applescript export and save commands not working.
    Tested on muliple mac OS versions

    4 votes

    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

    2 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

15. Scripting Windows: Add page item after add swatch will delete added swatch

    In ExtendScript on Windows only, adding any InDesign page item after adding a color will delete the color:
    
var doc = app.documents.add();
// adds black CMYK color
sw = doc.colors.add();
// this line will delete the color that was just added on Windows only
var rect = doc.rectangles.add();
alert(sw.isValid);


    This actually manifested for me as a crash bug. This script crashes InDesign 2024 Windows:

    var doc = app.documents.add();
    var sw = doc.colors.add();
    doc.rectangles.add({fillColor: sw});
    

    This crashes because the last line deletes the swatch when it adds the rectangle, then tries to use the swatch.

    1 vote

    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

    0 comments  ·  Scripting  ·  Edit…  ·  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

16. undo() does work, but spawns pointless error

    // ----
    function inner() {
    
        var doc = app.activeDocument;
        var i = doc.layers.length;
            while (i-->1) {
            doc.layers[i].remove();
        }
    }
    
    function outher() {
    
        app.doScript(inner,ScriptLanguage.JAVASCRIPT,[],UndoModes.SCRIPT_REQUEST,'outher');
        alert("pause");
        app.activeDocument.undo(); //<- wrong error, it actually works
    }
    
    app.doScript(outher,ScriptLanguage.JAVASCRIPT,[],UndoModes.ENTIRE_SCRIPT,'inner');
    
    // ----
    

    Also, this error is not ingnorable: if you put undo() in a try-clause, it doesnt work.

    Alsoalso, the different undo-modes (https://developer.adobe.com/indesign/dom/api/u/UndoModes/) are NOT sufficient explained. At least write some whole sentences on how they actually differ.

    2 votes

    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

    0 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

17. PlaceGun does not have reference to idms textframe

    Hi,

    I'm trying to place a textframe from an idms file into an indesign document. The actual loadPlaceGun() operation seems to work fine as I'm able to paste the textframe on the page. However, I also want to have a reference to that textframe. I was trying to accomplish this by using

    placeGun.pageItems.everyItem().getElements(), but it doesn't return any elements. I find this odd because I'm using the same method when inserting images and it works fine, so I'm not sure what the issue is. Link with pictures here: https://community.adobe.com/t5/indesign-discussions/placegun-does-not-have-reference-to-idms-textframe/m-p/14530065#M568624

    1 vote

    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

    0 comments  ·  Scripting  ·  Edit…  ·  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

18. My version is the latest, but I still can't use scripts "multipage importer". When I click on the script, the in-design program stops. I

    My version is the latest, but I still can't use scripts "multipage importer". When I click on the script, the in-design program stops.

    0 votes

    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

    0 comments  ·  Scripting  ·  Edit…  ·  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

19. hyperlinkTextSources.add thrown Errornumber 79111 since InDesign 2024

    When creating hyperlinks, a hyperlink is automatically created via a text object. The script ran until InDesign 2023.
    The text objects are returned by a search.

    app.activeDocument.findGrep();

    The hyperlink was created with the steps
    hyperlinkTextSources.add
    hyperlinkURLDestinations.add
    hyperlinks.add

    The first hyperlink is created as expected. In InDesign 2024, error 79111 "The selected object is already being used by another hyperlink" is thrown after the first hyperlink created (hyperlinkTextSources.add).

    1 vote

    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

    0 comments  ·  Scripting  ·  Edit…  ·  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

20. action feature

    hello, Is there an action feature in InDesign, like Photoshop?
    Is there a script that records the work steps and then applies the steps automatically when clicked?

    2 votes

    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

    0 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