4 Replies Latest reply on Feb 7, 2016 1:03 PM by Laubender

    [BUG] ID number of pageItem has changed after some path points are removed

    Laubender Adobe Community Professional & MVP

      Hi Extendscript scripters,

       

      this is a very special case I came accross today.

      I added an oval object to a page, opened the path with the menu command and removed two path points one after another.

      In the process of removing the second path point, the ID number of the object (now a polygon) suddenly changed.

       

      I cannot replicate this by scripting the whole process, but this phenenomen is very real when using InDesign's graphical user interface.

      And what's most interesting, it depends on the order of the pathpoints you remove, whether the new ID number is generated or not.

       

      We already had changing ID numbers with placed Adobe Illustrator files where a new ID was introduced after changing the layer visibility of such a file:

      https://forums.adobe.com/message/4922652#4922652

      https://forums.adobe.com/message/4929016#4929016

      https://forums.adobe.com/message/4929059#4929059

       

      For me, this is now the second case where surprisingly a page item is getting a new ID when working on it.

      Here the details summed up in three screenshots:

       

      The problem:

       

      TheProblem-ID-HasChangedAfterSecondPathPointWasRemoved.png

       

      Workaround 1:

       

      Workaround-1-UseDifferentOrderOfPathPoints.png

       

      Workaround 2:

       

      Workaround-2-RemoveTheTwoPathPointsTogether.png

       

      Note: You can never know what a user has done to an object, so, if there are some problems with stored ID numbers, remember this bug.

       

      Tested and seen with all versions of InDesign since CS3, namely:

       

      CS3 v5.0.4,

      CS4 v6.0.4,

      CS5 v7.0.4,

      on Mac OSX 10.6.8

       

      CS5.5 v7.5.3,

      CS6 v8.1.0,

      CC v9.3.0,

      CC 2014.2

      on Mac OSX 10.7.5.

       

      CC 2015.2 *

      on Mac OSX 10.10.3

       

       

      Best,

      Uwe

       

      * Not tested yet, but I bet this is not fixed.