50 results found

1. Duplicated AllPageItems collection when nesting Table inside another Table

   1 create new blank document, 1 page, no primary textframe
   2 creatte empty TextFrame,
   3 insert Table [2x2],
   4 insert another Table [2x2] to the 1st table - into 1st cell,
   5 insert another Table [2x2] to the 2nd table - into 1st cell,
   6 now insert image into 3rd table - from step 5 - as InLine object after a space - so the cell is not converted into Graphics cell,
   7 run script:

   var items = app.activeDocument.allPageItems;
   for (var i = 0; i < items.length; i++)
   $.writeln(items[i].toSpecifier());

   Expected result:

   /document[@id=1]//text-frame[@id=246]
   /document[@id=1]//rectangle[@id=286]
   /document[@id=1]//image[@id=282]

   Actual result:

   /document[@id=1]//text-frame[@id=246]
   /document[@id=1]//rectangle[@id=286]
   /document[@id=1]//image[@id=282]
   /document[@id=1]//rectangle[@id=286]
   /document[@id=1]//image[@id=282]
   /document[@id=1]//rectangle[@id=286]
   /document[@id=1]//image[@id=282]
   /document[@id=1]//rectangle[@id=286]
   /document[@id=1]//image[@id=282]
   Result: undefined

   Each nesting doubles the number of Images.

   1 create new blank document, 1 page, no primary textframe
   2 creatte empty TextFrame,
   3 insert Table [2x2],
   4 insert another Table [2x2] to the 1st table - into 1st cell,
   5 insert another Table [2x2] to the 2nd table - into 1st cell,
   6 now insert image into 3rd table - from step 5 - as InLine object after a space - so the cell is not converted into Graphics cell,
   7 run script:

   var items = app.activeDocument.allPageItems;
   for (var i = 0; i < items.length; i++)
   $.writeln(items[i].toSpecifier());

   Expected result:

   /document[@id=1]//text-frame[@id=246]
   /document[@id=1]//rectangle[@id=286]
   /document[@id=1]//image[@id=282]

   Actual result:

   /document[@id=1]//text-frame[@id=246]
   /document[@id=1]//rectangle[@id=286]
   /document[@id=1]//image[@id=282]
   /document[@id=1]//rectangle[@id=286]… 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

   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

2. Cell object is null!

   I get the third merged cell as null. Why is that?

   Please to get the error First create new document and table 3 by 3 and merge and select cells like screenshot. Execute the script.

   var sel = app.selection[0];
   var queuedCells = getQueuedCells ([sel]);
   function getQueuedCells (deepCells) {
   var queuedCells = new Array;
   if (deepCells.length > 0) {
   targetIndex = null;
   targetIndex = deepCells[0].parentRow.index;
   for (var dcs = 0; dcs < deepCells.length; dcs++) {
   for (var dcc = 0; dcc < deepCells[dcs].cells.length; dcc++) {
   alert ("(deepCells[" + dcs + "].cells[" + dcc + "] != null) " + (deepCells[dcs].cells[dcc] != null));
   if (targetIndex == deepCells[dcs].cells[dcc].parentRow.index) {
   queuedCells.push (deepCells[dcs].cells[dcc]);
   }
   }
   }
   }
   return queuedCells;
   }

   I get the third merged cell as null. Why is that?

   Please to get the error First create new document and table 3 by 3 and merge and select cells like screenshot. Execute the script.

   var sel = app.selection[0];
   var queuedCells = getQueuedCells ([sel]);
   function getQueuedCells (deepCells) {
   var queuedCells = new Array;
   if (deepCells.length > 0) {
   targetIndex = null;
   targetIndex = deepCells[0].parentRow.index;
   for (var dcs = 0; dcs < deepCells.length; dcs++) {
   for (var dcc = 0; dcc < deepCells[dcs].cells.length; dcc++) {
   alert ("(deepCells[" + dcs + "].cells[" + dcc + "] != null) " + (deepCells[dcs].cells[dcc] !=… more

   •  

   2 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

   3 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

3. Print Booklet

   Print Booklet error .. Won't print PDF, stops loading at page 6 of 16 page document quoting unknown error
   InDesign 2023 updated
   Critical document .. No Errors in document

   • 

   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

   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

4. AdobeXMPScript v 17.2.0.20

   Windows 10

   Adobe InDesign CC2022 (v 17.2.0.20)

   ExternalObject.AdobeXMPScript = new ExternalObject( "lib:AdobeXMPScript" )

   returns

   ERROR: 52, I/O error
   Unable to load the AdobeXMPScript library!

   • 

   7 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

   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

5. document.marginPreferences fails (at least on Mac0S)

   with (doc = app.documents.add()){
   with (marginPreferences){
   top = 10;
   left = 10;
   bottom = 10;
   right = 10;
   }
   }

   Results: margins are not set

   Expected: margins set

   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  ·  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

6. distribute

   document.distribute() doesn't allow aligning of pages.

   doc.distribute (doc.pages.everyItem(), DistributeOptions.HORIZONTAL_SPACE, true, 0)

   RESULT:
   Error: Invalid value of parameter "alignDistributeItems" of method "distribute". Expected array of PageItems, but received (Page,Page,Page).

   Expected: I can align pages in the UI via Align panel so I expect I can do the same in scripting.

   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  ·  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

7. Object Styles within Object Style Groups cannot be set to Document.pageItemDefaults (Scripting)

   See this thread in community forum: https://community.adobe.com/t5/indesign-discussions/script-cannot-set-an-object-style-as-a-default-frame-style-if-this-style-is-inside-a-folder/td-p/13062809

   If an object style is within a group, it cannot be assigned as the appliedTextObjectStyle in Document.pageItemDefaults. Have not checked whether the same is true for appliedGraphicObjectStyle

   4 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

   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

8. ScirptUI: in events `app.activate();` doesn’t work on Mac

   Version of Adobe InDesign
   all

   Steps to reproduce the issues
   * Build a ScriptUI palette with a button (or any other element).
   * Give the button a .onClick event with a app.activate; to give the programm’s focus back to InDesign.
   * Try to perform an InDesign shortcut (such as "command f" to show the built-in find dialog or any other you prefer).

   Expected result
   The focus of the programm should be given back to InDesign and the called action in InDesign should be performed (such as showing the find dialog).

   Actual result
   The focus remains on the ScriptUI palette and nothing happens.

   Stated here:
   https://community.adobe.com/t5/indesign-discussions/scriptui-palette-focus-after-clicking-button/td-p/10378801

   I can confirm this (non-)behaviour on Mac.

   Thanks,
   Tobias

   Version of Adobe InDesign
   all

   Steps to reproduce the issues
   * Build a ScriptUI palette with a button (or any other element).
   * Give the button a .onClick event with a app.activate; to give the programm’s focus back to InDesign.
   * Try to perform an InDesign shortcut (such as "command f" to show the built-in find dialog or any other you prefer).

   Expected result
   The focus of the programm should be given back to InDesign and the called action in InDesign should be performed (such as showing the find dialog).

   Actual result
   The focus remains on the ScriptUI palette and… 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

   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

9. Image catalogue script only has Desktop as a folder option. InDesign 2023

   When I've used this in previous editions, I was able to pick any folder on my computer. Now it only has Desktop as an option.

   •  

   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

   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

10. appliedLanguage property of text-related objects returns language from application, not document

    When I do configuration for a language in a document, such as setting doubleQuotes, this language can be found in the document object's list of languages and has a different id than the language with the same name in the application object's list.

    But when I access text inside the document – regardless what I inspect, paragraph, words, character, textStyleRange – I expect to get the language properties as set in the document, but instead I get those as set in the app.

    I believe this to be a software bug.

    More information as well as a workaround can be found in https://community.adobe.com/t5/indesign-discussions/paragraph-appliedlanguage-seems-to-differ-from-the-actual-applied-language/m-p/12997100#U12991700

    When I do configuration for a language in a document, such as setting doubleQuotes, this language can be found in the document object's list of languages and has a different id than the language with the same name in the application object's list.

    But when I access text inside the document – regardless what I inspect, paragraph, words, character, textStyleRange – I expect to get the language properties as set in the document, but instead I get those as set in the app.

    I believe this to be a software bug.

    More information as well as a workaround can be… more

    4 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

    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

11. Scripts using BridgeTalk do not work on M1 Macs (regardless of CC version)

    ID version: InDesign CC 2021 (16.3.2)
    OS: macOS Big Sur 11.5.2
    Processor: Apple M1

    When I try to run a script that uses BridgeTalk and works with Photoshop, it does not work.
    Also, a simple script using BridgeTalk will not work as well.
    Those scripts do work in CC 2021 on Intel Mac and macOS Big Sur 11.5.2.

    25 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

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

    Hi,

    The issue is under review.

    —

    Adobe InDesign Team

12. anchoredObjectSettings SpaceBelow is missing in the DOM

    The space below is missing for anchored Object Settings

    I can only find this:
    anchoredObjectSettings.anchorSpaceAbove

    (INDD17.1 + Javascript)

    2 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

    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

13. Convert Footnotes and Endnotes problem and a bonus scripting problem with special characters

    Indesign 17 on MacOs 12.3.1

    Convert Footnotes and Endnotes does not work when the footnotes does not have a footnote number.

    I have an Indesign document with footnotes.
    In each footnote I have removed the footnote number and the following tab character. (~F\t)

    I need these footnotes to be endnotes but this is not possible with the command "Convert Footnotes and Endnotes".

    Without the footnote number in the footnotes the command/script does not recognise the footnotes as being footnotes.

    They are however still footnotes and I can continue working with them as footnotes and also address them via scripting but the command "Convert Footnotes and Endnotes" does not work.

    I can reinsert a footnote number in each of the footnotes manually one by one by going through "Special Characters > Markers > Footnote Number.

    This will make the conversion work but this should not be necessary.

    Now to the bonus problem:

    I figured I could simply iterate the footnotes and insert the footnote number with a simple script. Guess what? Not that simple.

    I can insert everything except for the SpecialCharacters.FOOTNOTE_SYMBOL in the footnotes.
    Looking at the undo menu it appears as if indesign thinks it has inserted something as it says: "Undo Insert Text"
    But nothing was inserted.

    So ... I guess that I have two bugs here.

    Please help.

    Indesign 17 on MacOs 12.3.1

    Convert Footnotes and Endnotes does not work when the footnotes does not have a footnote number.

    I have an Indesign document with footnotes.
    In each footnote I have removed the footnote number and the following tab character. (~F\t)

    I need these footnotes to be endnotes but this is not possible with the command "Convert Footnotes and Endnotes".

    Without the footnote number in the footnotes the command/script does not recognise the footnotes as being footnotes.

    They are however still footnotes and I can continue working with them as footnotes and also address them via scripting but… more

    2 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

    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

14. External Object 'lib:AdobeXMPScript' not exist!

    Try to execute the attached code in the screenshot.
    And you will this error:

    Error Number: 52
    Error String: I/O Error

    •  

    18 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

    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
    Closed: Fixed  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

    This issue was fixed in InDesign version 16.3 that was released some time back.
    Closing this issue.

    —
    Adobe InDesign team

15. 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
    FIXED  ·  AdminRavi Kiran (Senior Lead Quality Engineer, 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

16. Section addition applescript splits last spread (applescript only)

    1. Version
       InDesign 16.4.1 CC2021 (macOS 10.16 Mojave)
       Only in applescript, not in javascript.

    2. Steps to reproduce the issues
       step1. prepare a spreads document. Total number of pages must be an odd number.
       step2. Use AppleScript to set the new section at even-numbered page.

    3. Expected result
       The state of the spread is not changed.

    4. actual result
       The spread at the end is split into two spreads.

    5. --code

    main()

    on main()
    mySetup() of me

    tell application "Adobe InDesign 2021"
    
        set mydoc to document 1
        set mypage2 to page 2 of mydoc
    
        tell mydoc
            set newsection to make section with properties {continue numbering:false, page start:mypage2, page number start:4}
        end tell
    end tell
    

    end main

    on mySetup()
    tell application "Adobe InDesign 2021"
    set mydoc to make document
    set properties of document preferences of mydoc to {facing pages:true, pages per document:5}
    end tell
    end mySetup

    -- code end

    In Japanese:

    見開きドキュメントを準備。総ページ数は奇数。
    任意の偶数ページにセクションを設定するスクリプトを実行すると、最終スプレッドが分割されてしまう。
    Applescriptでのみ発生して、javascript や手作業では発生しない。

    1. Version
       InDesign 16.4.1 CC2021 (macOS 10.16 Mojave)
       Only in applescript, not in javascript.

    2. Steps to reproduce the issues
       step1. prepare a spreads document. Total number of pages must be an odd number.
       step2. Use AppleScript to set the new section at even-numbered page.

    3. Expected result
       The state of the spread is not changed.

    4. actual result
       The spread at the end is split into two spreads.

    5. --code

    main()

    on main()
    mySetup() of me

    tell application "Adobe InDesign 2021"
    
        set mydoc to document 1
        set mypage2 to page 2 of mydoc
    
        tell mydoc
            set newsection to make section with properties {continue numbering:false,

    … 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

    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

17. InDesign does not load type library on upgrade

    Similar to the 2020 release (see https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/41072476-type-library-is-not-automatically-created-by-cc202), InDesign 2022 does not install the type library in upgrade. Please include this with the installation, as this will cause errors for many users.

    Error message: Error: Unable to load Adobe InDesign 2022 Type Library (Version 1.0).

    •  

    2 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

    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

18. cells selection

    Bug 1:

    See "Table 1" in the provided screenshot.
    Make a table with 3 columns and 3 rows.
    Merge the first 2 cells of the first row.
    Now you have 2 cells in the first row. (A and B).
    Set the contents of other cells to C, D, E, F, G, H.
    Now select cells B, D and E.
    If you click on the Edit menu, InDesign crash.
    If you choose File -> Export, InDesign crash.
    On the scripting side, calling document.selection throw an exception and it is not possible to get the current selection.

    Bug 2:
    See "Table 2" in the provided screenshot.
    Make a table with 2 columns and 4 rows.
    Split the second cells of the first row.
    Now you have 3 cells on the first row.
    Set the contents of the cells to numbers from 1 to 9.
    Now select cells 1, 2, 4, 5, 6, 7, 8, 9 (skip cell 3).
    Run this code:

    var doc = app.activeDocument;
    var selectedCells = doc.selection[0].cells;

    var i, ilen, contents = [];

    for (i = 0, ilen = selectedCells.length; i < ilen; i++) {
    contents.push(selectedCells[i].contents);
    }

    alert(contents.join('-'));

    expected result: 1-2-4-5-6-7-8-9
    current result: 1-2-3-4-5-6-7-8 (cell 3 is not part of the selection, cell 9 is missing).

    Applescript and VBscript don't have this problem, only ExtendScript.
    This happens with all versions of InDesign.

    Bug 1:

    See "Table 1" in the provided screenshot.
    Make a table with 3 columns and 3 rows.
    Merge the first 2 cells of the first row.
    Now you have 2 cells in the first row. (A and B).
    Set the contents of other cells to C, D, E, F, G, H.
    Now select cells B, D and E.
    If you click on the Edit menu, InDesign crash.
    If you choose File -> Export, InDesign crash.
    On the scripting side, calling document.selection throw an exception and it is not possible to get the current selection.

    Bug 2:
    See "Table 2"… 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

    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

19. AppleScript Finder communication

    InDesign version 16.3.2 with OSX 10.14.6 or later

    Indesign script‘s with calls to the Finder or other Apple apps work running from Apple’s Script Editor, but break when running from InDesign’s Scripts panel. Get an Not Authorized to Send Apple Events to Finder error.

    This breaks when running from the Scripts panel, but worked with InDesign 2020:

    tell application id "com.adobe.InDesign"
    tell application "Finder"
    activate
    display dialog "Hello"
    end tell
    end tell

    Calls to other Adobe apps are ok, so this still works from the panel:

    tell application id "com.adobe.InDesign"
    tell application id "com.adobe.Photoshop"
    activate
    display dialog "Hello"
    end tell
    end tell

    InDesign version 16.3.2 with OSX 10.14.6 or later

    Indesign script‘s with calls to the Finder or other Apple apps work running from Apple’s Script Editor, but break when running from InDesign’s Scripts panel. Get an Not Authorized to Send Apple Events to Finder error.

    This breaks when running from the Scripts panel, but worked with InDesign 2020:

    tell application id "com.adobe.InDesign"
    tell application "Finder"
    activate
    display dialog "Hello"
    end tell
    end tell

    Calls to other Adobe apps are ok, so this still works from the panel:

    tell application id "com.adobe.InDesign"
    tell application id "com.adobe.Photoshop"
    activate
    display dialog "Hello"
    end tell… more

    •  

    6 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

    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

20. findGrep() causes Indesign to hang and consume all available resources, eventually crashing the entire computer

    This code will cause InDesign 17.1 to hang and consume all available resources until the computer eventually runs out of both real and virtual memory and then crashes.

    app.findGrepPreferences = app.changeGrepPreferences = null;
    app.findChangeGrepOptions.properties = { includeMasterPages: true, kanaSensitive: true, widthSensitive: true };
    app.findGrepPreferences = null;
    app.findGrepPreferences.findWhat = '^(.*)$';

    var found = app.documents[0].changeObject.findGrep();

    If the runaway app is terminated using Task Manager (Windows 10), a stack of message boxes appear with the following message:
    Unable to terminate process
    The operation could not be completed
    The operation is not valid for this process

    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

    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