121 results found

1. Accessing Opacity Mask is impossible with scripting

   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

   • 

   17 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

2. [SDK Feature Request] Annotator option to draw selection annotation last.

   There is no option to draw the selection annotation last. Filled shapes and image annotations always block the selection annotation. See images for what i mean.

   •  

   •  

   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  ·  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. how can i call these functions in AI via script?

   -I would like to open a Multipage PDF with settings set to open "all pages" and "import pages as links".
   If the pdf has only one page import it also as a link (if possible do it)

   • Import an Illustrator *.ai file Multi-layouts by importing them as links across multiple layouts.

   • Set flattener presets:

   • preset name

   • various parameters...

   • Select all (Select / All)

   • Run the command: Object / convert transparency / Previously saved preset / OK

   • I saw among the commands that there is an openOptionsFreeHand could I create a script that opens the freehand files for me?

   How could I do? some things I found but others not.
   I can't find a manual that explains how to use the various script commands and options. All very technical and not very intuitive and detailed. An infinite list of commands but then how to use them is not understood.

   -I would like to open a Multipage PDF with settings set to open "all pages" and "import pages as links".
   If the pdf has only one page import it also as a link (if possible do it)

   • Import an Illustrator *.ai file Multi-layouts by importing them as links across multiple layouts.

   • Set flattener presets:

   • preset name

   • various parameters...

   • Select all (Select / All)

   • Run the command: Object / convert transparency / Previously saved preset / OK

   • I saw among the commands that there is an openOptionsFreeHand could I create a script that opens the freehand files for me?

   How could… 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  ·  JavaScripting  ·  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

4. settings raster effects value visible main screen

   I need to view somewhere in the Illustrator interface, the value set in the "raster effects settings" panel.

   Is there a scripted way to implement this?

   I've created actions that set this value to 72ppi / 300ppi so that I can change it when the document becomes heavy and unmanageable (thanks to using only 1 CPU CORE, thanks Adobe ❤).
   The problem is that if I save the file, I will probably save it at 72ppi, but for printing the effects are poor and you have to set them to 300ppi.
   So having the value always visible on the screen, I can have more control in knowing which value is set...
   The problem: Can it be done and how is it done?

   I need to view somewhere in the Illustrator interface, the value set in the "raster effects settings" panel.

   Is there a scripted way to implement this?

   I've created actions that set this value to 72ppi / 300ppi so that I can change it when the document becomes heavy and unmanageable (thanks to using only 1 CPU CORE, thanks Adobe ❤).
   The problem is that if I save the file, I will probably save it at 72ppi, but for printing the effects are poor and you have to set them to 300ppi.
   So having the value always visible on the screen,… 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  ·  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. exportFile doesn't work with NoUI document

   trying to create a "NoUI" document and export as SVG like this:

   opendoc = app.documents.addDocumentNoUI();
   opendoc.exportFile(file, ExportType.SVG);

   I get the attached error in AI

   I can't think of any other way to export an SVG via script. Obviously there are scripting things that don't work with NoUI documents, but it seems like this one should. Am I doing something wrong?

   •  

   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  ·  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. app.selectTool('Adobe Intertwine Zone Marker Tool') does not work

   When I run the following script, the Adobe Intertwine Zone Marker Tool starts up and I can select the area where I want to change the overlap like the lasso tool. However, nothing happens after the selection.

   app.selectTool('Adobe Intertwine Zone Marker Tool')
   

   Expected Result

   The overlap of the selected area is changed.

   Actual Result

   The line will remain as if it was drawn with the lasso tool. The overlap is not changed.

   Enviroment

   • macOS 11.7
   • Illustrator 27.1.1

   • 

   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

   6 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
   Resolved (Comments Open)  ·  AdminEgor Chistyakov (Admin, Adobe Illustrator) responded

   An intended way of picking up the hidden Zone Marker tool via a script is to enter the Intertwine mode using these commands:

   app.executeMenuCommand('Partial Rearrange Make') — when an intertwine object is not created yet, and

   app.executeMenuCommand('Partial Rearrange Edit') — when the object already exists, as per comments by the OP.

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

   •  

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

   • 

   • 

   • 

   10 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

9. AppleScript can't get character properties (ver26.4.1, ver26.5)

   tell character 1
   properties
   end

   ver26.3.1 get properties
   but, ver26.4.1, ver26.5 cant't get properties

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

10. Illustrator 2022 (26.5.0) listStyle scripting issues

    Starting with Illustrator 2022 (26.4.1), the ability to create bulleted and numbered lists has been implemented. Text to which lists are applied can be obtained in ExtendScript or AppleScript by using the listStyle property.

    However, normal text that is not bulleted and numbered lists (hereinafter called "normal text") has no listStyle assigned to it, and referencing it causes an error. The following problem occurs.

    Issue 1: ExtendScript and AppleScript cannot directly change lists to normal text

    Expected state

    For example, the following script (ExtendScript) can change a paragraph to normal text.

    var doc = app.documents[0] ;
    var targetParagraph = doc.selection[0].paragraphs[0] ;
    var noListStyle = doc.listStyles.getByName('None') ; // no exists
    targetParagraph.listStyle = noListStyle ;
    

    Actual state

    Indirectly change a paragraph to normal text by applying a predefined paragraph style, etc.

    Issue 2: Cannot get paragraph properties in AppleScript

    Steps to reproduce

    1. Prepare a text frame without lists applied in the document
    2. With it selected, run the following AppleScript

    tell application "Adobe Illustrator"
        set target_paragraph to paragraph 1 of (item 1 of (selection of document 1))
        properties of target_paragraph -- error
    end tell
    

    Expected result

    The properties of the target paragraph can be retrieved as record.

    {character offset:1, length:11, contents:"Lorem ipsum"...}
    

    Actual result

    Exit with error.

    error "Adobe Illustrator got an error: Internal error" number 1200
    

    Environment:

    • Illustrator 2022 (26.5.0)
    • macOS 11.6.8

    Illustrator 2022 (26.5.0) の箇条書きをスクリプトで扱うときの問題

    Illustrator 2022 (26.4.1)から，箇条書きを作る機能が実装された。箇条書きが適用されたテキストは，ExtendScriptやAppleScriptではその形式をlistStyleプロパティで調べられる。

    しかし，箇条書きでない通常のテキスト（以後通常テキストと呼ぶ）にlistStyleが割り当てられておらず，参照するとエラーが起こる。そして次のような問題を呼ぶ。

    Issue 1: ExtendScriptやAppleScriptでは，直接箇条書きを通常テキストに変更できない

    期待する状態

    例えば次のようなスクリプト（ExtendScript）で通常テキストに変更できる。

    var doc = app.documents[0] ;
    var targetParagraph = doc.selection[0].paragraphs[0] ;
    var noListStyle = doc.listStyles.getByName('None') ; // no exists
    targetParagraph.listStyle = noListStyle ;
    

    実際の状態

    事前に定義した段落スタイルを適用するなどして，間接的に通常テキストに変更する。

    Issue 2: AppleScriptで段落のpropertiesを取得できない

    再現手順

    1. 書類に箇条書きが適用されていないテキストフレームを用意する
    2. それを選択した状態で，次のAppleScriptを実行する

    tell application "Adobe Illustrator"
        set target_paragraph to paragraph 1 of (item 1 of (selection of document 1))
        properties of target_paragraph -- error
    end tell
    

    期待する結果

    対象の段落のプロパティがrecordとして取得できる。

    {character offset:1, length:11, contents:"Lorem ipsum"...}
    

    実際の結果

    エラーで終了する。

    error "Adobe Illustratorでエラーが起きました: Internal error" number 1200
    

    環境：

    • Illustrator 2022 (26.5.0)
    • macOS 11.6.8

    Starting with Illustrator 2022 (26.4.1), the ability to create bulleted and numbered lists has been implemented. Text to which lists are applied can be obtained in ExtendScript or AppleScript by using the listStyle property.

    However, normal text that is not bulleted and numbered lists (hereinafter called "normal text") has no listStyle assigned to it, and referencing it causes an error. The following problem occurs.

    Issue 1: ExtendScript and AppleScript cannot directly change lists to normal text

    Expected state

    For example, the following script (ExtendScript) can change a paragraph to normal text.

    var doc = app.documents[0] ;
    var targetParagraph = doc.selection[0].paragraphs[0]

    … more

    • 

    11 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

11. variables.removeAll(); does not work

    When I execute variables.removeAll();. error occurred: 1346458189 ('PARM').
    On the other hand, dataSets.removeAll() works.

    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  ·  JavaScripting  ·  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. ExtendScript Debugger 2.0.3 for VSCode fails on "doScript" method

    When a script containing "doScript" method is run from VSCode to AI 2022 using any version of ExtendScript Debugger 2.x it locks up Ai 2022 requiring a force quit. VSCode must also be reloaded before any debugging can continue.

    Rolling ExtendScript Debugger back to v1.1.2 eliminates the failure at the expense of the more advanced features of v2.x.

    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  ·  JavaScripting  ·  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. Variable font support in scripts

    There doesn't seem to be any way to use variable fonts in scripts. There is an undocumented property TextFont.axisVector, but it is read-only. So there is no way to adjust the axes of a variable font via script, even though Illustrator has supported variable fonts for many years now.

    Relevant thread:
    https://community.adobe.com/t5/illustrator-discussions/scripting-variable-fonts-in-illustrator/td-p/9834514

    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

    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

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

    •  

    11 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

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

16. Please update "Planet X" in backend to "Live Paint"

    Actions read from API are named "Planet X".
    In AI menu, they are "Live Paint"

    Additionally, there is one typo: "Marge Planet X" = "Merge Live Paint"

    When Loupedeck reads the actions from API, they appear with outdated names in Loupedeck UI.

    •  

    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  ·  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. Please update JavaScript engine to ES6
    52 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  ·  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

18. Join command is unavailable when run from an action via a script

    We have an action that works, when launched form the Actions panel.
    Operations are simple:
    1. Copy
    2. Deselect All
    3. Paste in Front
    4. Join
    5. Join
    It is designed to create a new closed shape from two segments from different shapes.

    However, when we call this exact action from a script with a app.doScript, it doesn’t work, an error message 'The object "Join" is not currently available' is displayed.

    Please see the video.

    • 

    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

    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

19. Unexpected reset of selected swatches

    app.activeDocument.swatches.getSelected() gets selected swatches in the document. If you select one path in a document and apply any selected color to it, the swatches will remain selected. But if many paths are selected, applying a swatch to any path resets the selected swatches.

    The user has to manually select the swatches again each time he runs the scripts.

    15 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

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

    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

    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