41 results found

1. 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

2. 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,
   We have been able to reproduce the issue and it is currently under investigation.

   —

   Adobe InDesign Team

3. 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

4. ID 2020 bug - checkbox not shown.

   in ID2019 everything is Ok - the checkbox is visible. But in 2020 - not!

   var w = new Window("dialog");
   var list = w.add ("listbox", undefined, ["One", "Two", "Three", "Four"]);
   list.items[1].checked = true;
   w.show();

   •  

   8 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
   Under Review  ·  amaarora responded

   Thanks for reporting the issue
   We are reviewing it

   -InDesign Team

5. 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

6. 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

7. [Scripting] Document.findObject() incorrectly targets activeDocument

   System: Indesign 18.4, MacOS 13.4.1

   To reproduce:
   1. Open two documents, each with a filled frame 100% tint.
   2. Run attached script "findObject bug.js"
   3. Note the console output.
   4. Refer to this forum post for notes and commentary.

   Expected result:
   doc.findObject() will return found items from both open documents.

   Actual result:
   doc.findObject() returns only items from active document.

   Note that using app.findObject() is not a viable workaround in some cases, such as the issue in this post.

   •  

   • 

   •  

   5 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

8. 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

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

10. InDesign incorrect font.version when SUBSTITUED

    In an InDesign document when a font.status is SUBSTITUED, both the xmpTPg:Fonts/Resource/stFnt:versionString and also font.version property show the value of the font which is used by InDesign for the substitute font, and not the original (now missing) font version.

    As anyone who has worked with font purchasing knows, the font version is extremely important. Both because of licensing reasons (previously purchased font licenses for font versions may need to be repurchased with newer versions), and also because even in a font produced by the same foundry or designer, a minor version change can include optical differences, spacing differences causing text reflow, overset text and glyph errors.

    Here's an example

    1) Open the attached document into Adobe InDesign
    2) In the top dropdown menu, go to Type > Find/Replace Fonts
    3) In the Find/Replace Fonts listing there is only one font and it is missing/substituted, SharpGroteskBook22
    4) In the Find/Replace Fonts listing for the font in the “More Info” area the version is correctly shown as “Version 1.003”
    5) However, when showing the properties of this font in Visual Studio Code Adobe Extendscript debugger the font.version for this font is incorrectly shown as: "version: 17.0d1e1" (see screenshot)
    6) Also when viewing the metadata for the document in the File > File Info > Raw fonts xmpTPg:Fonts object, the versionString is incorrectly shown as “SharpGroteskBook2217.0d1e1” (see screenshot)

    I am considering this behavior to be a bug.

    In my opinion there is no value which is gained from InDesign having the font.version of a totally different font which is only being used to substitute a font which is not found.

    Why does the font.version property not continue to return the value of the font when it was INSTALLED?

    The data is not entirely missing. There is a location in InDesign which contains the accurate font version for a font which is font.status = SUBSTITUTED, and that is in the InDesign UI Fonts > Find/Replace Fonts menu, More Info area. I need a way to be able to retrieve that accurate data via scripting.

    InDesign and InDesign Server versions 2023, 2022, 2020 etc.

    In an InDesign document when a font.status is SUBSTITUED, both the xmpTPg:Fonts/Resource/stFnt:versionString and also font.version property show the value of the font which is used by InDesign for the substitute font, and not the original (now missing) font version.

    As anyone who has worked with font purchasing knows, the font version is extremely important. Both because of licensing reasons (previously purchased font licenses for font versions may need to be repurchased with newer versions), and also because even in a font produced by the same foundry or designer, a minor version change can include optical differences, spacing differences causing text… more

    •  

    •  

    •  

    3 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. InDesign: Insert authors document's metadata without quotes

    Version
    Adobe InDesign up to 2023.

    Steps to reproduce the issues
    Setting the active document’s metadataPreferences.author with multiple authors, separated by comma or semicolon in a string via extendscript:
    
app.activeDocument.metadataPreferences.author = "Elric Wade; Anne Emu; Sophie Kumpir";


    Expected result
    The authors should be placed into the "Author" metadata field, separated by comma or semicolon.

    Actual result
    The authors are placed into the "Author" metadata field, but all set within double quotes, so they appear to be one author, not multiple authors.

    Test file, screenshot, video or GIF capturing the issue (optional)
    See attached screenshot.

    Please make it possible to add multiple authors (e.g. with not quoting comma or semicolon separated strings, or by letting pass-in an array with names).

    Version
    Adobe InDesign up to 2023.

    Steps to reproduce the issues
    Setting the active document’s metadataPreferences.author with multiple authors, separated by comma or semicolon in a string via extendscript:
    
app.activeDocument.metadataPreferences.author = "Elric Wade; Anne Emu; Sophie Kumpir";


    Expected result
    The authors should be placed into the "Author" metadata field, separated by comma or semicolon.

    Actual result
    The authors are placed into the "Author" metadata field, but all set within double quotes, so they appear to be one author, not multiple authors.

    Test file, screenshot, video or GIF capturing the issue (optional)
    See attached screenshot.

    Please make it possible to add… more

    •  

    3 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

12. matchPreviewBackgroundToThemeColor resets pasteboardMargins to [0,0]

    In a script, app.activeDocument.pasteboardPreferences.matchPreviewBackgroundToThemeColor to 1 causes app.activeDocument.pasteboardPreferences.pasteboardMargins to reset to [0,0].

    Furthermore, setting the pasteboardMargins doesn't work after setting app.activeDocument.pasteboardPreferences.matchPreviewBackgroundToThemeColor to 1.

    (While matchPreviewBackgroundToThemeColor is set to 0 everything works fine.)

    3 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

13. masterSpread.primaryTextFrame can't be set in jsx

    See: https://community.adobe.com/t5/indesign-discussions/create-primarytextframe/m-p/13362907#M503701

    The primaryTextFrame property under masterSpread doesn't seem to work. If there is an existing PTF on the spread, then mySpread.primaryTextFrame.isValid resolves as true, but it cannot be set to NothingEnum.NOTHING/null, and a non-PTF on the spread cannot be assigned to mySpread.primaryTextFrame.

    3 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. email QR Codes don't work with MATMSG formatting

    InDesign 18.1 on Mac OS 13.2.1 Ventura - Data merge for email QR codes specifically doesn't work, and your documentation is frankly non-existent. Using the MATMSG format doesn't produce a working QR with Data Merge, but using HTML format mailto in Plain Text does. I'm sure I'll run into the wrong version VCARD problem soon, too.

    This is consistent using the MATMSG format in a .csv with data Merge. Using the manual entry isn't a workable option due to the quantity of codes being generated.

    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

15. 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

16. 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

17. 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

18. script panel blank

    Nenhum Script aparece no painel. Todos sumiram, e todos os scripts estão na pasta do ID.

    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

19. FindChangeByList not working

    1 The script stopped working. Doesn’t do anything.

    2 Please let the updater copy the FindChangeList.txt from the previous version. In most cases it’s part of a workflow that breaks with each update.

    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

20. Actions Panel like in Photoshop and Illustrator

    If this existed in Indesign like it does in Photoshop and Illustrator it would save me HOURS of time. Please please make this happen,

    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