111 results found

1. [CS6 to 2020 15.0.1.209] documentPreferences.snippetImportUsesOriginalLocation | values true and false do the opposite what they should do

   Hi,
   if I set value for snippetImportUsesOriginalLocation of documentPreferences to true, InDesign will place a snippet file with spread.place( snippetFile ) always at the current zero point [0,0].

   Wheras I set the value to false the snippet will be placed at its original position.

   It should be exactly the other way.

   Currently value false will use the original position and value true will chose the current zero point as defined with app.documents[0].zeroPoint .

   Tested with German InDesign versions:
   CS6 8.1.0
   CC 2014 10.2.
   2020 v. 15.0.1.209
   All on WIndows 10.

   In the discussion linked to below Gerald Singelmann can see this also on a Mac OSX-version of InDesign:

   https://www.hilfdirselbst.ch/gforum/gforum.cgi?post=573538#573538

   Regards,
   Uwe Laubender
   ( ACP )

   Hi,
   if I set value for snippetImportUsesOriginalLocation of documentPreferences to true, InDesign will place a snippet file with spread.place( snippetFile ) always at the current zero point [0,0].

   Wheras I set the value to false the snippet will be placed at its original position.

   It should be exactly the other way.

   Currently value false will use the original position and value true will chose the current zero point as defined with app.documents[0].zeroPoint .

   Tested with German InDesign versions:
   CS6 8.1.0
   CC 2014 10.2.
   2020 v. 15.0.1.209
   All on WIndows 10.

   In the discussion linked to below Gerald Singelmann can see… 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  ·  Java Script  ·  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. Collapse Treeview not working

   On Indesign CC (Win or Mac) :
   Treeview with multi levels can be expand with recursive function;
   But collapse operation seems to be not working with similar function;

   On Indesign CS6 (Win or Mac) :
   Treeview with multi levels can be expand.
   Collapse operation runs halfway. But items (not node) on first level are indented too much.

   Run Script treeviewexpandcollapse.jsx to test it

   • 

   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

   2 comments  ·  Java Script  ·  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. 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 index of "Page_263.index+1". I think, in other situations, the work around will require a loop.

   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… 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  ·  Java Script  ·  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  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

   We’re reviewing this issue.

   —
   Adobe InDesign team

4. Script failing ... strangely

   Instructions:

   1. Load Script.txt into ExtendScript CC
   2. Open ID CC 2019
   3. Connect ExtendScript CC to ID CC 2019
   4. Run the script
   5. Observe that the script gives an error on line 6 (Invalid object for this request.) This is because TextFrame281 and TextFrame284 are the same object. They should be different objects.

   To see this more clearly:

   1. Load script.txt into ExtendScript CC
   2. Open ID CC 2019
   3. Connect ExtendScript CC to ID CC 2019
   4. Uncomment line 4 (var temp = TextFrame_281.id)
   5. Run the script
   6. The script runs fine. If you look in the document that has been created, the two text frames are in the upper right corner and they are linked to each other.

   In other words, the value of TextFrame_281 changes, depending on whether it is accessed. My only guess is that this is some kind of lazy evaluation gone wrong.

   Instructions:

   1. Load Script.txt into ExtendScript CC
   2. Open ID CC 2019
   3. Connect ExtendScript CC to ID CC 2019
   4. Run the script
   5. Observe that the script gives an error on line 6 (Invalid object for this request.) This is because TextFrame281 and TextFrame284 are the same object. They should be different objects.

   To see this more clearly:

   1. Load script.txt into ExtendScript CC
   2. Open ID CC 2019
   3. Connect ExtendScript CC to ID CC 2019
   4. Uncomment line 4 (var temp = TextFrame_281.id)
   5. Run the script
   6. The script runs fine. If you look in the document that has been created, the two text… 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  ·  Java Script  ·  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

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

   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

   5 comments  ·  Java Script  ·  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

6. Setting stroke weight to 0 by script results in 1 pt

   Given a frame (graphic or text) with stroke color set to 'None' and stroke weight set to 0, the jsx command "app.selection[0].strokeWeight = 0" sets the weight to 1pt and stroke color to the default swatch.

   Steps to reproduce:

   1. Create a new Document.
   2. Create a new Text (or Graphic) Frame.
   3. Set the stroke weight to 0 and color to 'None' if necessary
   4. Select the frame with the Selection tool.
   5. Start a script with a following one line: app.selection[0].strokeWeight=0

   Expected result: no change
   Actual result: stroke weight set to 1pt and color to the default swatch.

   Note:
   Setting stroke weight to any other value behaves as expected.

   InDesign CC2018 v13.0.1

   Given a frame (graphic or text) with stroke color set to 'None' and stroke weight set to 0, the jsx command "app.selection[0].strokeWeight = 0" sets the weight to 1pt and stroke color to the default swatch.

   Steps to reproduce:

   1. Create a new Document.
   2. Create a new Text (or Graphic) Frame.
   3. Set the stroke weight to 0 and color to 'None' if necessary
   4. Select the frame with the Selection tool.
   5. Start a script with a following one line: app.selection[0].strokeWeight=0

   Expected result: no change
   Actual result: stroke weight set to 1pt and color to the default swatch.

   Note:
   Setting stroke weight to… more

   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

   6 comments  ·  Java Script  ·  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. La nueva versión indesign 2020 ya no tiene la opción de Flip page para flash.

   La nueva versión indesign 2020 ya no tiene la opción de Flip page para flash.

   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  ·  InDesign Server  ·  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. SDK

   Suport C++SDK

   • 

   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  ·  C++ SDK  ·  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. 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).

   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  ·  C++ SDK  ·  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 now available in the latest versions of InDesign – version 16.0 and above.
   Please update to this version to get the fix.

   —
   Adobe InDesign team

10. Bug When Overriding Master Page Items: Unexpected Shift of Master Page Objects

    When overriding page items by script, those items are unexpectedly shifted and do not stay in the x/y position, they are on the master page. This differs widely from the UI-behaviour of InDesign.

    There is a very good view and analysis of this bug from Marc Autret, which can be found here:
    http://www.indiscripts.com/post/2014/06/indesign-scripting-forum-roundup-6#hd1sb2

    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

    7 comments  ·  Java Script  ·  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. Able to change administrators through profile login
    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  ·  InDesign Server  ·  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

12. Allow for control of undo tracking Re: Undo Set Scripting Tag

    Currently the only way to manipulate the undo queue is to run a script with doScript and even then it's very limiting. With my current event listeners, the user clicks around a few times and the undo queue fills up with 'Undo Set Scripting Tag' and they are unable to undo simple changes without holding down CTRL+Z for a few seconds. I am unable to use doScript because I need to return values to my interface. I would like to suggest an option to temporarily suspend undo tracking during certain script actions. Some of my actions do not change the document and only update the interface.

    Currently the only way to manipulate the undo queue is to run a script with doScript and even then it's very limiting. With my current event listeners, the user clicks around a few times and the undo queue fills up with 'Undo Set Scripting Tag' and they are unable to undo simple changes without holding down CTRL+Z for a few seconds. I am unable to use doScript because I need to return values to my interface. I would like to suggest an option to temporarily suspend undo tracking during certain script actions. Some of my actions do not change the… 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  ·  Java Script  ·  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

13. textStyleRange.convertToNote() becomes very confused.

    I'll attach a self-contained script which first creates in order to demonstrate problems with textStyleRange.convertToNote(). The script creates a small document containing "b"s. These are marked with a smaller pointSize so that they form individual textStyleRanges. The script then converts these textStyleRanges into notes. Unfortunately, the script terminates with a message: "Object is invalid; tsr.convertToNote()". This message happens because the scripting engine has become confused and is trying to convert a "b" within a note into another note. This shouldn't happen and is the first problem.

    Open the story window. The beginning of the story has a clear pattern of notes between sentences. This should continue to the end of the document, but looking further down, two more problems can be seen:

    (1) Overflow.jpg shows that the text at the frame's overflow boundary has become confused. It should say "The quick green fox ...", but instead it says something like "The The The quick The ...".

    (2) Nearer to the end of the story, Confusion.jpg shows that larger phrases are converted into notes even though only "b" should be converted.

    I can't attach a script, so here it is:

    // Run this script in InDesign CC 2019, Roman Region.
    //THIS IS THE PROBLEM PART THE REST IS JUST TO SET IT UP.

    // Convert all "b" characters into notes
    function hideNotes(story){

     // Find all the "b"s
     app.findTextPreferences = null;
     var findPrefs = app.findTextPreferences;
     findPrefs.findWhat = "b";
     var matchingItems = story.findText()
    
     // It shouldn't be necessary to copy the findText() results, but just in case ...
     var copy = []
     for (var i = 0; i < matchingItems.length; i++) { 
         copy[i] = (matchingItems[i])
     }
    
     // Loop through the "b"s and convert them to notes
     for (var i = 0; i < copy.length; i++) { 
         var tsr = copy[i].textStyleRanges.firstItem();
         tsr.convertToNote();
      }
    

    }

    // This is just setting up a document with reasonable defaults
    function setup(){

    // Set up application
    var millimeterMeasurementUnits = 2053991795; // This means millimeters
    app.viewPreferences.verticalMeasurementUnits = millimeterMeasurementUnits ;
    app.viewPreferences.horizontalMeasurementUnits = millimeterMeasurementUnits ;
    
    // Set up new document
    var doc = app.documents.add();
    doc.zeroPoint = [0, 0];
    doc.viewPreferences.rulerOrigin = 1380143215 // This means PageOrigin;
    doc.documentPreferences.pageWidth = 210
    doc.documentPreferences.pageHeight= 297
    doc.marginPreferences.left  = 20
    doc.marginPreferences.right  = 20
    doc.marginPreferences.top  = 20
    doc.marginPreferences.bottom  = 20
    
    // Set up new page
    var page = doc.pages.firstItem();
    page.marginPreferences.left  = 20
    page.marginPreferences.right  = 20
    page.marginPreferences.top  = 20
    page.marginPreferences.bottom  = 20
    
    // Set up new frame
    var textFrame = doc.textFrames.add();
    textFrame.geometricBounds = [20, 20, 277, 190];
    
    // Add frame text
    for(var i = 0; i < 250; i++){
        var insertionPoint = textFrame.insertionPoints.lastItem()
        insertionPoint.pointSize = 12
        insertionPoint.contents = "The quick green fox jumped over the lazy dog. "
        insertionPoint = textFrame.insertionPoints.lastItem()
        // This point size will set the "b" into its own textStyleRange
        insertionPoint.pointSize = 7
        insertionPoint.contents = "b"
    }
    

    }

    //Entry Point
    setup();
    var stories = app.activeDocument.stories;
    for (var i = 0; i < stories.length; i++) {
    hideNotes(stories[i]);
    }

    I'll attach a self-contained script which first creates in order to demonstrate problems with textStyleRange.convertToNote(). The script creates a small document containing "b"s. These are marked with a smaller pointSize so that they form individual textStyleRanges. The script then converts these textStyleRanges into notes. Unfortunately, the script terminates with a message: "Object is invalid; tsr.convertToNote()". This message happens because the scripting engine has become confused and is trying to convert a "b" within a note into another note. This shouldn't happen and is the first problem.

    Open the story window. The beginning of the story has a clear pattern of… 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

    1 comment  ·  Java Script  ·  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. Where to find InDesign document links API reference?

    Where do I find the API reference for document links? (As show in the Links tab.) I've found scripting guides and various bits of documentation, but I can't find a complete object model reference.

    Newcomer to InDesign scripting. All I need is to dump the full path of every linked image to a text file. I've found a script online which does this, but it only outputs each link's 'name'. A fuller version of the same script dumps out the size and file type as well.

    I'd like to modify this script to dump out 'path', but 'path' doesn't seem to be the property name, and I can't figure out where to find the list of property names. Am I missing something? Does this documentation exist?

    Where do I find the API reference for document links? (As show in the Links tab.) I've found scripting guides and various bits of documentation, but I can't find a complete object model reference.

    Newcomer to InDesign scripting. All I need is to dump the full path of every linked image to a text file. I've found a script online which does this, but it only outputs each link's 'name'. A fuller version of the same script dumps out the size and file type as well.

    I'd like to modify this script to dump out 'path', but 'path' doesn't seem… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Apple Script  ·  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. IDML resources

    On https://www.adobe.com/devnet/indesign/documentation.html site links are not working at the IDML section. Please fix it!

    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  ·  InDesign Server  ·  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
    Need More Info  ·  amaarora responded

    The links are working fine for me.
    Can you recheck once at your end?

    Thanks

16. The Script FindChangeByList.jsx not working CC2019

    Dont Working script

    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  ·  Java Script  ·  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. Allow keyboard shortcuts to be assigned by script

    Add the ability to assign keyboard shortcuts do built-in InDesign menu actions or panel menus by javascript.

    14 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  ·  Java Script  ·  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. Separate the indesign scripting forum from the indesign community support forum

    With the relaunch of Adobe's community support forums, the indesign scripting forum was merged with the general indesign forum. Please separate the two so users can find the most relevant content.

    45 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

    19 comments  ·  Java Script  ·  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
    Partial Fix  ·  amaarora responded

    Hi,
    1. The majority of InDesign Scripting threads were merged and archived at first.
    2. After a month or so, InDesign Scripting re-appeared as its own topic in the new forums.
    3. David K. started un-archiving older threads last week, a few at a time, very slowly and by hand, because of odd server-side limitations.
    4. There is no “Direct Link” to the Scripting Topic at this time, but this ought to be fixed with the current sprint from the forums team. The internal bug number is: ALFD-1530

    While we wait for ALFD-1530, there is a backdoor way to find direct links to topics. You can follow a topic then look at your follows… or just use these links:

    • InDesign Scripting: https://community.adobe.com/t5/forums/filteredbylabelpage/board-id/indesign/label-name/scripting
    • InDesign SDK: https://community.adobe.com/t5/forums/filteredbylabelpage/board-id/indesign/label-name/sdk
    • InDesign Server Developers: https://community.adobe.com/t5/forums/filteredbylabelpage/board-id/indesign/label-name/server%20developers

    Thanks

19. GREP Find and replace Script not working CC2019

    We are getting below error while running the GREP script in InDesign CC2019, but same is working fine in CS6 version. Please check and fix this bug quickly to migrate CC2019 version.

    Error: User canceled this action

    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

    5 comments  ·  Java Script  ·  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. 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, it is not!

    Note:
    In case of a placed InDesign page or a PDF exported from an InDesign document with layers intact, all InDesign layers are nested in one "layer group" so we have to look after graphicLayers[0] (that's the "layer group") and add graphicLayers.everyItem() to access all sub-layers.

    app.selection[0].graphics[0].graphicLayerOptions.graphicLayers[0].graphicLayers.everyItem().currentVisibility = false;

    Actual Result:
    Error message thrown. In my German InDesign this is:
    "Die angeforderte Aktion konnte nicht ausgeführt werden, da das Objekt nicht mehr existiert."
    This is the $ID/ObjectDeletedError

    Expected Result:
    No error message. The visibility of all graphic layers should change.

    Any Workarounds:
    Loop the graphic layers. But do so that every time you do not access a reference to the graphic by its ID number.

    Something like that will work:

    var layerLength = app.selection[0].graphics[0].graphicLayerOptions.graphicLayers[0].graphicLayers.length;

    for(var n=0;n<layerLength;n++)
    {
    $.writeln( n+"\t"+app.selection[0].graphics[0].id );
    app.selection[0].graphics[0].graphicLayerOptions.graphicLayers[0].graphicLayers[n].currentVisibility = false;
    };

    The following will NOT work:

    var graphicLayers = app.selection[0].graphics[0].graphicLayerOptions.graphicLayers[0].graphicLayers.everyItem().getElements();

    for(var n=0;n<graphicLayers.length ;n++)
    {
    graphicLayers[n].currentVisibility = false;
    };

    Why will that not work?
    See into the results in the JavaScript Console with $.writeln( n+"\t"+app.selection[0].graphics[0].id ); from the loop that is working.
    Everytime you change currentVisibility of a graphicLayer the ID of the graphic is changing. That means the object is not itself anymore.

    Here some sample output from the JavaScript Console with one of my sample files:
    /*
    Result:
    0 325
    1 331
    2 337
    3 343
    4 349
    */

    You can see that the graphic began with a ID number of 325, after changing currentVisibility of the first graphic layer it suddenly became ID 331 and so on.

    Read about this scripting issue in the InDesign Scripting Forum here:

    "Place specific pdf layer into indesign with javascript"
    Yuliascript 18.06.2018
    https://forums.adobe.com/message/10452540#10452540

    Also here a thread from 2012:
    "Activating object layers basing on document layers"
    Marco Lugli 14.12.2012
    https://forums.adobe.com/message/4920745#4920745

    Also see attached documents with a placed sample PDF:

    PlacedPDFwithLayers-13.1.0.76.zip

    Download link from my Dropbox:
    https://www.dropbox.com/s/hfsspv5ddxaakvy/PlacedPDFwithLayers-13.1.0.76.zip?dl=0

    FWIW: Did this bug report also at Bug ID - ID-4208697.

    Regards,
    Uwe Laubender
    ( ACP )

    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,… more

    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

    1 comment  ·  Java Script  ·  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