Adobe InDesign: SDK/Scripting Bugs and Features

  1. XSLX Import partially fails on Windows

    The problem is while manual import of XSLX files is no worries, it partially fails when the placement is called from script on Windows.
    The main issue is that sheetName property seems to be ignored leading to the first sheet always being placed no matter which sheetName has been set.
    The expected behaviour is that the sheetName set in app.excelImportPreferences.sheetname is correctly placed.
    No problem with old xls format or with xlsx on mac.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Java Script  ·  Flag idea as inappropriate…  ·  Admin →
  2. Scripting | graphicLayerOptions : Changing visibility of graphicLayer will change ID number of placed graphic

    Problem Description:
    If you change the visibility of a graphicLayer of a placed graphic, could be a PDF, a PSD, an InDesign page or a AI file, the ID number of the placed graphic will change. The result of this is, that "everyItem().doSomething" with object graphicLayer will not work at all.

    Steps to Reproduce:
    1. Place a graphic with some graphic layers.
    2. Access the graphic layers of the graphic by scripting and try to change eg. currentVisibility for all graphic layers in one go.
    Frame holding the graphic is selected. The script snippet below should do this easily. However,…

    5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Java Script  ·  Flag idea as inappropriate…  ·  Admin →
  3. [15.0.0.155] New property Alternate Text for Hyperlinks is not supported by Scripting, IDMS and IDML

    Hi,
    I see no new property for a new feature with InDesign 2020 version 15.0.0.155:
    Alternate Text for Hyperlinks.

    The feature is also missing with IDMS and IDML.

    Regards,
    Uwe Laubender
    ( ACP )

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Java Script  ·  Flag idea as inappropriate…  ·  Admin →
  4. Bug in IXMLOutStream.h header file

    InDesign2020SDK/source/public/interfaces/xmedia/IXMLOutStream.h:499

    void WriteName(const UTF16TextChar* name, bool16 newLine = kFalse)
    
    { this->WriteName(name, newLine); }

    This function calls itself. It leads to a stack overflow on Windows but the code analyzer in Xcode catches it and reports an error during compilation. It can be changed to:

    void WriteName(const UTF16TextChar* name, bool16 newLine = kFalse)
    
    { this->WriteName(WideString(name), newLine); }

    and it will work (it calls the previous function in the file instead).

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  C++ SDK  ·  Flag idea as inappropriate…  ·  Admin →
  5. A reference to panel item 25 breaks a script

    There's a rogue panel that breaks InDesign CC2019 when it is referenced (CC2018 is not affected).

    Open InDesign CC2019, then run this one-line script:

    app.panels[25].name

    Result: Error: 'Invalid object for this request'.

    Now do this:

    app.panels[25].isValid

    which returns true.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Java Script  ·  Flag idea as inappropriate…  ·  Admin →
  6. nextItem() doesn't work

    Instructions:


    1. Load Script4.txt into ExtendScript CC

    2. Open ID CC 2019

    3. Connect ExtendScript CC to ID CC 2019

    4. Run the script

    5. Observe that line 8 gives an "Object is invalid" error. That's because the nextItem() on line 6 didn't work.

    To see this more clearly:


    1. Load Script4.txt into ExtendScript CC

    2. Open ID CC 2019

    3. Connect ExtendScript CC to ID CC 2019

    4. Comment line 6 and uncomment line 7.

    5. Run the script

    6. The script runs fine. It prints out "2", the name of the second page.

    In other words, nextItem() is broken. The work around (in this case) is to use an…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Java Script  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Adobe InDesign: SDK/Scripting Bugs and Features

Categories

Feedback and Knowledge Base