118 results found

1. Make the (Black) Color Swatch a TRUE BLACK

   In the Appearance Panel, the (Black) color swatch is not a TRUE BLACK color and when this color swatch is used and a file is exported to PDF, Rich black is not achieved.

   The attached document shows a few shapes that are black. The top right is a true black color and the color swatch had to be changed from the standard (BLACK) color swatch in order to be achieved when exporting to a PDF. The left and bottom color swatches have the (Black) color swatch from the appearance panel applied.

   Please, Please, Please, make the (Black) color swatch a true rich black color (since users cannot adjust this color).

   Since the standard (Black) color swatch isn't true black, it will take me quite a bit of time to apply a new color to all my previously designed files that use your standard (Black) color swatch.

   In the Appearance Panel, the (Black) color swatch is not a TRUE BLACK color and when this color swatch is used and a file is exported to PDF, Rich black is not achieved.

   The attached document shows a few shapes that are black. The top right is a true black color and the color swatch had to be changed from the standard (BLACK) color swatch in order to be achieved when exporting to a PDF. The left and bottom color swatches have the (Black) color swatch from the appearance panel applied.

   Please, Please, Please, make the (Black) color swatch a… 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

   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

2. PreflightScope not working

   PreflightOptions.preflightScope in InDesign has not worked since at least CS 5.5. No matter what value is used, preflight checks the whole document. Here is a sample script (error for color image <250 ppi) that the issue can be tested:

   var currDoc = app.documents[0];
   if (app.preflightProfiles.itemByName("export").isValid){
           app.preflightProfiles.itemByName("export").remove();
   }
   var pfProfile = app.preflightProfiles.add({name: "export"});
   var pfResRule = pfProfile.preflightProfileRules.add("ADBE_ImageResolution", {flag: PreflightRuleFlag.returnAsError});
   pfResRule.ruleDataObjects.add("color_min_res", RuleDataType.realDataType, 250);
   currDoc.preflightOptions.preflightScope = '1-2';
   var pfProcess = app.preflightProcesses.add(currDoc, pfProfile);
   pfProcess.waitForProcess();
   pfResults = pfProcess.aggregatedResults[2];
   $.writeln(pfResults);
   

   ––> with a 3-page document with problems on pages 2 and 3, InDesign reports both problems despite the scope been set to ‘1-2’ (same with ‘1’ and ‘1,2’)

   We would very much like to speed our preflight process and get rid of the tedious parsing of preflight results only to discard pages not set in the scope.

   One additional note on its behavior that could be fixed, too: if you define a scope that includes page numbers not in the document, either as
   - a range e.g. "1-5" when document has pages numbers 1,4,5,6,... or
   - e.g. "14" when the document has only 12 pages
   ––> InDesign throws an error "Error 30477: Invalid value for set property 'preflightScope'. Expected PreflightScopeOptions enumerator or String, but received "1-5".", which is quite misleading.

   PreflightOptions.preflightScope in InDesign has not worked since at least CS 5.5. No matter what value is used, preflight checks the whole document. Here is a sample script (error for color image <250 ppi) that the issue can be tested:

   var currDoc = app.documents[0];
   if (app.preflightProfiles.itemByName("export").isValid){
           app.preflightProfiles.itemByName("export").remove();
   }
   var pfProfile = app.preflightProfiles.add({name: "export"});
   var pfResRule = pfProfile.preflightProfileRules.add("ADBE_ImageResolution", {flag: PreflightRuleFlag.returnAsError});
   pfResRule.ruleDataObjects.add("color_min_res", RuleDataType.realDataType, 250);
   currDoc.preflightOptions.preflightScope = '1-2';
   var pfProcess = app.preflightProcesses.add(currDoc, pfProfile);
   pfProcess.waitForProcess();
   pfResults = pfProcess.aggregatedResults[2];
   $.writeln(pfResults);
   

   ––> with a 3-page document with problems on pages 2 and 3, InDesign reports both problems despite the scope been set to ‘1-2’ (same with ‘1’… 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

   2 comments  ·  CEP  ·  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
   We are reviewing the issue

   -InDesign Team

3. Scripted iterative document open/close fails to close files

   Note: my sample code is jsx, but the problem may not be limited to jsx. Change the filetype of my provided files from txt to jsx prior to using!

   We have multiple products that sometimes show a problem with document.close() not actually closing the file, leading to incorrect functioning, memory bloat, slowdowns, and we believe some crashes. I provide a test script that takes a currently open document and iteratively copies it, opens the copy, then closes the copy -- after the loop is finished, the copy files are removed.

   Important: If run from the ESTK or Scripts Panel, the script works as expected -- no problems. If run from a custom menu (setup script also provided), the problem happens every time.

   We believe we've seen this in cases where a custom menu is not the launch mechanism, and may be intermittent in those cases.

   We believe we've seen this in InDesign Server as well. My scripts have been tested in CC 2019 and CC 2020 and on both Win and Mac.

   In order to run the "Test_menu.jsx" script for using a custom menu, the "Documents left open on close.jsx" script must be in a "TestScripts" folder in your 'home' or 'user' folder (i.e., inside of "~/TestScripts").

   This problem is a real headache and is difficult to work around. It affects multiple product areas; we urge prompt attention to this problem.

   Thanks.

   Note: my sample code is jsx, but the problem may not be limited to jsx. Change the filetype of my provided files from txt to jsx prior to using!

   We have multiple products that sometimes show a problem with document.close() not actually closing the file, leading to incorrect functioning, memory bloat, slowdowns, and we believe some crashes. I provide a test script that takes a currently open document and iteratively copies it, opens the copy, then closes the copy -- after the loop is finished, the copy files are removed.

   Important: If run from the ESTK or Scripts Panel, the… 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  ·  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

4. Scripted iterative document open/close fails to close files

   Note: my sample code is jsx, but the problem may not be limited to jsx.

   We have multiple products that sometimes show a problem with document.close() not actually closing the file, leading to incorrect functioning, memory bloat, slowdowns, and we believe some crashes. I provide a test script that takes a currently open document and iteratively copies it, opens the copy, then closes the copy -- after the loop is finished, the copy files are removed.

   Important: If run from the ESTK or Scripts Panel, the script works as expected -- no problems. If run from a custom menu (setup script also provided), the problem happens every time.

   We believe we've seen this in cases where a custom menu is not the launch mechanism, and may be intermittent in those cases.

   We believe we've seen this in InDesign Server as well. My scripts have been tested in CC 2019 and CC 2020 and on both Win and Mac.

   In order to run the "Test_menu.jsx" script for using a custom menu, the "Documents left open on close.jsx" script must be in a "TestScripts" folder in your 'home' or 'user' folder (i.e., inside of "~/TestScripts").

   This problem is a real headache and is difficult to work around. It affects multiple product areas; we urge prompt attention to this problem.

   Thanks.

   Note: my sample code is jsx, but the problem may not be limited to jsx.

   We have multiple products that sometimes show a problem with document.close() not actually closing the file, leading to incorrect functioning, memory bloat, slowdowns, and we believe some crashes. I provide a test script that takes a currently open document and iteratively copies it, opens the copy, then closes the copy -- after the loop is finished, the copy files are removed.

   Important: If run from the ESTK or Scripts Panel, the script works as expected -- no problems. If run from a custom menu (setup… 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. Enable XML export in Word file format so tagging and attributes are preserved.

   InDesign cannot currently export an XML structured file in Word file format, either because Word does not recognize the tags and attributes or because those elements are not within the document content. Please make an export possible so that XML structured content can be exported in Word file format and then reimported into InDesign.

   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

6. inDesign crash with documents.loadMasters()

   i have try to load master page by script (i post a small script test) but indesign crash... if i want copy masterspread from doc1 to doc 2 i must use "duplicate"...

   target indesign

   // create two document
   var doc1 = app.documents.add()
   var doc2 = app.documents.add()

   // add new master spread and set it
   var master = doc1.masterSpreads.add()
   master.namePrefix = "XX"

   // save document on disk and get file
   doc1.save()
   var doc1File = doc1.filePath

   // close
   doc1.close()

   // load master spreads of doc1 on doc 2
   doc2.loadMasters(doc1File)

   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

7. Make ImageCatalog Script an integral contact sheet function in InDesign

   Good morning. There is a sample script in InDesign that I LOVE! It makes contact sheets much quicker (and using far less memory) than Photoshop or Bridge. If you have a hundred images and want to make a contact page, this script is the way to go. Much more efficient. The Script is the ImageCatalog under JavaScript samples in the Scripts window. This has always been available, and always worked very well until the last couple of updates. Now when I run it, it just sits there. If I try saving the images again (save a copy) or saving them as a different format (jpeg vs tiff or tiff vs jpeg), sometimes it works. Again - I LOVE this script, and wish you would just make it a regular feature. Is there something I should be doing with my images before I run the script?

   These are sample scripts that ship with InDesign. They show up under Windows / Utilities / Scripts / Samples / JavaScript / ImageCatalog.jsx. There is no vendor to contact other than Adobe for this one. There is another version of this under Windows / Utilities / Scripts / Samples / AppleScript / ImageCatalog.jsx, but I've never been able to get the AppleScript version to work.

   Good morning. There is a sample script in InDesign that I LOVE! It makes contact sheets much quicker (and using far less memory) than Photoshop or Bridge. If you have a hundred images and want to make a contact page, this script is the way to go. Much more efficient. The Script is the ImageCatalog under JavaScript samples in the Scripts window. This has always been available, and always worked very well until the last couple of updates. Now when I run it, it just sits there. If I try saving the images again (save a copy) or saving them… 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

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

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

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

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

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

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

    Thanks for reporting the issue. We are reviewing it

    -InDesign Team

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

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

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

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

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

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

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

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