101 results found

1. kAINamedStyleListChangedNotifier is not emitted when a Graphic Style is updated

   If you hold ALT and drag some art into a Graphic Style, it updates, but the notifier is not sent. This has been happening since at least the original CC. It used to work before that.

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

2. kATEDocumentResourceChangedNotifier not sent when character/paragraph styles are changed

   According to the documentation for kATEDocumentResourceChangedNotifier, it is supposed to be "Sent when ATE document resources, such as named style, have changed."

   I have never found this to be true, in any version since the ATE was added. This has always been a serious pain point, because we build small previews of text styles and we have to rebuild them every time we open a UI that shows them, because we have no way of knowing if they have changed (or if they even still exist, or any have been added!).

   Since it's never been sent before, there can't be much code expecting it -- so how much downside could there be to suddenly start sending them correctly?

   According to the documentation for kATEDocumentResourceChangedNotifier, it is supposed to be "Sent when ATE document resources, such as named style, have changed."

   I have never found this to be true, in any version since the ATE was added. This has always been a serious pain point, because we build small previews of text styles and we have to rebuild them every time we open a UI that shows them, because we have no way of knowing if they have changed (or if they even still exist, or any have been added!).

   Since it's never been sent before, there can't be… 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

   0 comments  ·  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

3. [Typo] Document.rearrangeArtboards() of Illustrator JavaScript Reference.pdf

   There is a typo in rearrangeArtboards in Illustrator JavaScript Scripting Reference.pdf. It cannot execute as per the document. Please correct it.

   I have checked and it was wrong from CS5 to current version (2022 v2 - Feb 2022).

   Expected Name:

   rearrangeArtboards

   Actual Name:

   rearrangeArboards ("t" is missing from Artboards)

   •  

   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

   0 comments  ·  JavaScripting  ·  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. GraphicStyle Aspect

   Hello,

   I develop a plugin where I need to create/update/modify graphic style and/or Aspect for graphic item.
   I try many solutions, search on the web but for the moment it's not possible.

   Could you please add support for creating/editing/deleting graphic style and aspect ?
   It's very important for me ! And I think many developpers can be interesting with this features.

   Thanks a lot !
   Loïc

   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

   0 comments  ·  JavaScripting  ·  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. Transparency Mask

   There is no way to work with the transparency mask in the Script SDK. This is the least of the problems. But when creating scripts to modify objects with masks, developers expect masks to be modified along with the parent object. After all, we see the "Linked to Art" icon in the Transparency panel.

   But what we have all these years as script developers: resize(), position, translate() modify the object, and its mask remains as it was.

   I've counted about 10 of my own scripts that use similar commands. I also have a large collection of other developers' scripts, where about 70 scripts contain similar commands. So none of them will help users automate operations with their art.

   More than once I've had users come to me and ask, "Where did the opacity mask go after I ran the script? The only solution is to add dynamic actions with Move, Scale with calling app.doScript(). But this introduces many other problems and inconveniences.

   There is no way to work with the transparency mask in the Script SDK. This is the least of the problems. But when creating scripts to modify objects with masks, developers expect masks to be modified along with the parent object. After all, we see the "Linked to Art" icon in the Transparency panel.

   But what we have all these years as script developers: resize(), position, translate() modify the object, and its mask remains as it was.

   I've counted about 10 of my own scripts that use similar commands. I also have a large collection of other developers' scripts, where… 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  ·  JavaScripting  ·  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. Drag-and-drop bug running scripts containing app.doScript()

   Watch the "drag-and-drop-bug.mp4" video, which demonstrates a specific but with the Adobe Illustrator's JS engine handling scripts which are dragged to different areas of the screen in different ways.

   In most cases, a drag-and-dropped script will work as intended. But for 10 years in CS6-CC 2023 versions there is a limited bug handling the script if dragged to the “wrong” area of the program window.

   If the script contains an action and a user drags it onto the document window, it may not work correctly. If the script selects objects one by one and applies an action to them, it won't work on the first selected object, but it will work on all the others.

   If you drag the script to the document tab area, the action will be called correctly for each selected object.

   So far, the problem is found in scripts that use actions with the commands from the Transform menu: Move, Rotate, Reflect, Scale, Shear.

   Try it yourself:
   1) Rename "ScriptSet.txt" to "ScriptSet.aia" and load it in the Actions panel.
   2) Rename the "rotate-180-action.txt" file to "rotate-180-action.js" and try running the script in a document with multiple artboards.

   Here's the Medium article about this issue:
   https://aiscripts.medium.com/running-scripts-via-drag-and-drop-84021c505ed4

   Watch the "drag-and-drop-bug.mp4" video, which demonstrates a specific but with the Adobe Illustrator's JS engine handling scripts which are dragged to different areas of the screen in different ways.

   In most cases, a drag-and-dropped script will work as intended. But for 10 years in CS6-CC 2023 versions there is a limited bug handling the script if dragged to the “wrong” area of the program window.

   If the script contains an action and a user drags it onto the document window, it may not work correctly. If the script selects objects one by one and applies an action to them, it… 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  ·  JavaScripting  ·  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. Activating artboard with a script does not update the Artboards panel

   If you click inside of an artboard with a mouse, it gets the 'active' flag and becomes selected in Artboards panel as well. So if you press Shift+O to pick Artboard Tool, you see its name and dimensions.
   However, if you use method setActiveArtboardIndex() — the artboard still gets the active black border, but the panel stays unrefreshed, and if you pick the tool you get the information about a different artboard.

   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

   1 comment  ·  JavaScripting  ·  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. Isolate/Unisolate commands

   Commands:
   //menu Other Object\Isolate Selected Object
   app.executeMenuCommand('enterFocus');

   //menu Other Object\Exit Isolation Mode
   app.executeMenuCommand('exitFocus');

   Return error:
   an Illustrator error occurred: 1346458189 ('PARM').

   This applies not only to isolation, but also to some other commands.

   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

   1 comment  ·  JavaScripting  ·  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. Opacity Mask

   Transparency / Opacity Mask - In layers pallet page item names look different with masks (underline) and opacity masks (dashed). It would be great if you could add this to properties of the page item like mask: none, opacity mask or mask. Identifying these objects is even harder then Envelopes which can only be identified by identifying as plugin object. Worst case putting info in the tag propery would be better then nothing when cresating it. I do not believe a opacity mask can be identified through any form of SDK/Script which makes identifying raster images in the file impossible. The other option would be to have the raster item still listed when it is part of opacity mask. Also on this site an option should be all so that not SDK/Script specific.

   Transparency / Opacity Mask - In layers pallet page item names look different with masks (underline) and opacity masks (dashed). It would be great if you could add this to properties of the page item like mask: none, opacity mask or mask. Identifying these objects is even harder then Envelopes which can only be identified by identifying as plugin object. Worst case putting info in the tag propery would be better then nothing when cresating it. I do not believe a opacity mask can be identified through any form of SDK/Script which makes identifying raster images in the file impossible.… 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  ·  JavaScripting  ·  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. CEP: Unique identifier for items and layers

    Please provide unique identifiers for all page items and layers via script.

    Right now it is not possible to save IDs of page items/layers in a variable or array and retrieve them at a later point in the script.

    At first I could not believe it that there are no IDs. This is total basic and should be a no-brainer and default.
    Thanks!

    P.S. Current workaround: set custom tag on items. This works only as long as the user is not duplicating an items. Than you have two items with the same tag and it is not unique anymore.
    Workaround here is my other feature request: receive events from AI in a CEP panel: https://illustrator.uservoice.com/forums/908050-sdk-scripting-bugs-and-features/suggestions/36902764-cep-waaaay-more-events-from-ai-to-cep-panels-e-g

    Please provide unique identifiers for all page items and layers via script.

    Right now it is not possible to save IDs of page items/layers in a variable or array and retrieve them at a later point in the script.

    At first I could not believe it that there are no IDs. This is total basic and should be a no-brainer and default.
    Thanks!

    P.S. Current workaround: set custom tag on items. This works only as long as the user is not duplicating an items. Than you have two items with the same tag and it is not unique anymore.
    Workaround… 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

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

11. [Typo] ExportOptionsTIFF.IZWCompression of Illustrator JavaScript Reference.pdf

    There is a typo in ExportOptionsTIFF in Illustrator JavaScript Scripting Reference.pdf, which fails to specify whether or not LZW compression is used. Please correct it.

    I have checked and it was wrong from the CS6 version.

    Expected Name: lZWCompression (begins with a lowercase L)
    Actual Name: IZWCompression (begins with an uppercase i)

    The function name in the example is also wrong. exportFileToTIFF should be correct.

    Exporting to TIFF format
    
    // Exports current document to dest as a TIFF file with specified
    // options, dest contains the full path including the file name
    
    function exportFileToPSD (dest) { // <-- exportFileToTIFF
      if ( app.documents.length > 0 ) {
        var exportOptions = new ExportOptionsTIFF();
        var type = ExportType.TIFF;
        var fileSpec = new File(dest);
        exportOptions.resolution = 150;
        exportOptions.byteOrder = TIFFByteOrder.IBMPC;
        exportOptions.IZWCompression = false;
        app.activeDocument.exportFile( fileSpec, type, exportOptions );
      }
    }
    

    There is a typo in ExportOptionsTIFF in Illustrator JavaScript Scripting Reference.pdf, which fails to specify whether or not LZW compression is used. Please correct it.

    I have checked and it was wrong from the CS6 version.

    Expected Name: lZWCompression (begins with a lowercase L)
    Actual Name: IZWCompression (begins with an uppercase i)

    The function name in the example is also wrong. exportFileToTIFF should be correct.

    Exporting to TIFF format
    
    // Exports current document to dest as a TIFF file with specified
    // options, dest contains the full path including the file name
    
    function exportFileToPSD (dest) { // <-- exportFileToTIFF
      if

    … more

    •  

    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  ·  JavaScripting  ·  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. Wrong short-discription in omv.xml

    macOS10.14.7 / IllustratorCC 26.3.1

    In the following omv file, the shortdesc(short description) of each property of the "TextAntialias" class in lines 833 to 865 is identical to the one for the previous "TextType" class.
    （以下のomvファイル、833行目〜865行目の「TextAntialias」クラスの各プロパティのショートディスクリプションが一つ前のTextTypeのものと同一です。）

    /Library/Application Support/Adobe/Scripting Dictionaries CC/Illustrator 2022/omv.xml

    ...
    <classdef name="TextAntialias" enumeration="true">
    <shortdesc>The type of text antialiasing.</shortdesc>
    <elements type="class">
    <property name="NONE" rwaccess="readonly">
    <shortdesc>Text from a point.</shortdesc>
    <datatype>
    <type>int</type>
    <value>1</value>
    </datatype>
    </property>
    <property name="SHARP" rwaccess="readonly">
    <shortdesc>Text within an area.</shortdesc>
    <datatype>
    <type>int</type>
    <value>2</value>
    </datatype>
    </property>
    <property name="CRISP" rwaccess="readonly">
    <shortdesc>Text on a path.</shortdesc>
    <datatype>
    <type>int</type>
    <value>3</value>
    </datatype>
    </property>
    <property name="STRONG" rwaccess="readonly">
    <shortdesc>Text on a path.</shortdesc>
    <datatype>
    <type>int</type>
    <value>4</value>
    </datatype>
    </property>
    </elements>
    </classdef>
    ...

    macOS10.14.7 / IllustratorCC 26.3.1

    In the following omv file, the shortdesc(short description) of each property of the "TextAntialias" class in lines 833 to 865 is identical to the one for the previous "TextType" class.
    （以下のomvファイル、833行目〜865行目の「TextAntialias」クラスの各プロパティのショートディスクリプションが一つ前のTextTypeのものと同一です。）

    /Library/Application Support/Adobe/Scripting Dictionaries CC/Illustrator 2022/omv.xml

    ...
    <classdef name="TextAntialias" enumeration="true">
    <shortdesc>The type of text antialiasing.</shortdesc>
    <elements type="class">
    <property name="NONE" rwaccess="readonly">
    <shortdesc>Text from a point.</shortdesc>
    <datatype>
    <type>int</type>
    <value>1</value>
    </datatype>
    </property>
    <property name="SHARP" rwaccess="readonly">
    <shortdesc>Text within an area.</shortdesc>
    <datatype>
    <type>int</type>
    <value>2</value>
    </datatype>
    </property>
    <property name="CRISP" rwaccess="readonly">
    <shortdesc>Text on a path.</shortdesc>
    <datatype>
    <type>int</type>
    <value>3</value>
    </datatype>
    </property>
    <property name="STRONG" rwaccess="readonly">
    <shortdesc>Text on a path.</shortdesc>
    <datatype>
    <type>int</type>
    <value>4</value>
    </datatype>
    </property>
    </elements>… more

    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  ·  JavaScripting  ·  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. Justification bug, cannot set 'center' in v24.2 using AppleScript

    Running a script to set the justification of text works perfectly for left and right, but no longer works for center. Putting the example script given in the latest Illustrator CC Scripting Guide, page 122, into a Script Editor visually compiles centre differently to left and right and only works if you remove or comment out the line justifying to center.

    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

    3 comments  ·  AppleScript  ·  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. Concerns about the future of CEP and UXP

    I've been reading through the new information about UXP and the announcement that it will be replacing CEP.

    If this happens it will likely mean the end of our current CEP extension, since the support provided in UXP does not cover our use case. To be specific we have problems with the following areas:

    1) Most critical UXP is "not a browser" and as such will only support a subset of HTML. Our extension relies on being able to run another web application within the browser control supplied by CEP, in an iframe window. While there is currently no list of supported HTML, it seems likely that iframe will not be a supported HTML element.

    This will break our CEP extension.

    2) No support for persistent panels. Currently there is only support for Modal Dialogs, which are expect to be invoked and then closed. Our CEP extension relies upon a persistent control, which the user logs into once.

    3) In ability to access the user file system, in particular the Download directory. This will break a few features in our application which rely on being able to read information from this directory.

    I've been reading through the new information about UXP and the announcement that it will be replacing CEP.

    If this happens it will likely mean the end of our current CEP extension, since the support provided in UXP does not cover our use case. To be specific we have problems with the following areas:

    1) Most critical UXP is "not a browser" and as such will only support a subset of HTML. Our extension relies on being able to run another web application within the browser control supplied by CEP, in an iframe window. While there is currently no list… more

    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  ·  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

15. Executing Extendscript/Javascript from the C++ API

    As far as I know there is no possible way to execute an Extendscript via the C++ API.
    In InDesign we can do so by providing the script as a string and fetching simple output results.

    Our customers can customize our Plugins by providing their own script in our custom scripting language. Unfortunately our language does not cover all use cases and needs to be constantly expanded. With support for Extendscript/Javascript execution from the C++ API we could circumvent the problem and give the users a lot of flexibility and power.

    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

    2 comments  ·  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

16. access opacity of TextRange

    There is no way to access the opacity of a textRange. This TextFrame has 100% opacity, but it contains two textRanges, one of which is at 50% opacity. I don't believe that there is a way to make everything 100% opaque from javascript.

    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

    3 comments  ·  JavaScripting  ·  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. When art is renamed, no notifier is sent

    In CC2019, at least two notifiers should result from renaming art: kAIArtPropertiesChangedNotifier & kAIArtObjectsChangedNotifier, but neither is sent.

    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

    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

18. Adjust dashes to corner and path ends via scripting

    I have dashed lines in my drawing and want to align dashes to corners and path ends. No problem in the Illustrator stroke menu. There are two buttons with dashed lines on it. But there is no script command to do this.

    Please add script command for adjust dashes.

    •  

    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  ·  Vb 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. [BUG] Extend script via Javascript document.importFile broken between CC2017 and CC2018

    Currently this is producing an error in CC2018 Illustrator on Mac

    var newFile = new File('/tmp/sample.rtf');
    app.activeDocument.importFile(newFile, false);

    Works correctly in CC2017.

    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

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

20. Scripting Bug: importFile() no longer works in CC2018

    importFile() worked fine in CC2017, now in CC2018 it throws an "Illegal Argument" error.

    here's a small JavaScript to test. Open any document or create a blank file before running the script

    var f = File('c:/temp/Example File.pdf'); // to test, add a path to a valid file in your system

    var idoc = app.activeDocument; // have any document open

    idoc.importFile(f, false);

    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  ·  JavaScripting  ·  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