Skip to content

Illustrator (Desktop) SDK/Scripting Issues

← Adobe Illustrator

How can we improve Adobe Illustrator (Desktop) SDK?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

131 results found

  1. variables.removeAll(); does not work

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

    1 vote
    1 comment  ·  JavaScripting  ·  Admin →
    How important is this to you?

  2. 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
    0 comments  ·  JavaScripting  ·  Admin →
    How important is this to you?

  3. 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
    0 comments  ·  JavaScripting  ·  Admin →
    How important is this to you?

  4. [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
    …
    11 votes
    1 comment  ·  JavaScripting  ·  Admin →
    How important is this to you?

  5. 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>…

    5 votes
    0 comments  ·  JavaScripting  ·  Admin →
    How important is this to you?

  6. 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
    1 comment  ·  JavaScripting  ·  Admin →
    How important is this to you?

  7. Please update JavaScript engine to ES6

    53 votes
    5 comments  ·  JavaScripting  ·  Admin →
    How important is this to you?

  8. 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
    0 comments  ·  JavaScripting  ·  Admin →
    How important is this to you?

  9. 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
    1 comment  ·  JavaScripting  ·  Admin →
    How important is this to you?

  10. 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
    1 comment  ·  JavaScripting  ·  Admin →
    How important is this to you?

  11. ExtendScript経由のスクリーン用に書き出しが固まる

    説明

    ExtendScript経由で［スクリーン用に書き出し］を実行すると動作が遅くなり，動いていないように見えます（実際は動いていて長い時間待てば終わる）。その間レインボーカーソルが出ています。

    JPEGを書き出すときに顕著です。書き出す画像がある程度大きいと，プログレスバーが99%くらいになった後ほとんど進みません。CPU使用率は100%前後になります。

    例：1700x1000pxのアートボード8枚を300ppiで書き出すとき，かかる時間は228.175秒（できたJPEGの重さは1点につき2.9MB）

    同じ条件の書き出しをGUIから手動で実行すると，すぐに終わります。

    例：1700x1000pxのアートボード8枚を300ppiで書き出すとき，かかる時間は2秒くらい（できたJPEGの重さは1点につき1.8MB）

    PNG24は手動よりは遅いですが，JPEG程大きく影響しません。CPU使用率は160%前後でした。

    例：1700x1000pxのアートボード8枚を300ppiで書き出すとき，かかる時間は57.745秒

    次の条件で起こります。
    * 少なくともIllustrator 2020〜2022(24.3.0〜26.0.2)
    * 少なくともmacOS Monterey 12.0.1(Apple Silicon) / Big Sur 11.6(Apple Silicon)の2環境
    * 少なくともMacBook Air(Apple Silicon, 16GBメモリ) / iMac(Apple Silicon, メモリ不明)の2機種
    * ExtendScriptのDocument.exportForScreens経由で実行
    * オプションJPG 100，300ppi(アートボードサイズは1700x1000px)

    次の条件では起こりません。
    * オプションをJPG 100，72ppiにしたとき
    * オプションをPNG24，300ppiにしたとき
    * GUIから手動で実行したとき

    次の項目はあまり影響しないようです。
    * IllustratorをRosettaで起動するかどうか。Rosettaにしたらさらに遅くなる
    * アートボード上のアイテムを単純なデータにすること。四角いパスとグラデーションだけでも遅くなる

    期待する動作

    ExtendScript経由で［スクリーン用に書き出し］を実行したとき，GUI経由で行うのと同じくらい速く動きます。

    4 votes
    0 comments  ·  Admin →
    How important is this to you?

  12. exportForScreens() file output naming issues

    Natively File > Export > Export for Screens has an option to add a suffix to the output file name, but in scripting the last parameter adds a prefix to the output file name not a suffix as it should to match the desk top user options.

    exportForScreens(path, ExportForScreensType, ExportForScreensOptions, ExportForScreensItemToExport, "This adds a prefix NOT a suffix");

    1 vote
    0 comments  ·  JavaScripting  ·  Admin →
    How important is this to you?

  13. I'm a graphic design student, my work and projects depend on Adobe Illustrator. The program does not run on my new Windows 11 Surface Pro X

    Adobe Illustrator for devices with ARM-64 Processors (i.e. Surface Pro X)

    1 vote
    2 comments  ·  C++ SDK  ·  Admin →
    How important is this to you?

  14. Update the VSCode ExtendScript Debugger

    This is an essential tool.

    Too many issues to mention here - and that's just on a PC. It doesn't work at all on ARMx64

    https://marketplace.visualstudio.com/items?itemName=Adobe.extendscript-debug&ssr=false#review-details

    The community needs this kept up to date!

    3 votes
    0 comments  ·  JavaScripting  ·  Admin →
    How important is this to you?

  15. firstLineIndent can’t be set to zero

    Create a text object, type some text, keep it selected and run the script:

    activeDocument.textFrames[0].paragraphs[0].paragraphAttributes.firstLineIndent = 20;
    alert(activeDocument.textFrames[0].paragraphs[0].paragraphAttributes.firstLineIndent);

    activeDocument.textFrames[0].paragraphs[0].paragraphAttributes.firstLineIndent = 0;
    alert(activeDocument.textFrames[0].paragraphs[0].paragraphAttributes.firstLineIndent);

    You have two alerts saying 20, while the second one should show and actually set the first line indent value to 0 — and it does not.

    5 votes
    2 comments  ·  JavaScripting  ·  Admin →
    How important is this to you?

  16. Constrain Proportions button toggle

    app.preferences.setBooleanPreference('linkTransform',1);
    makes the Constrain Width and Height Proportions button to toggle... but only internally, the button does not change.

    16 votes
    1 comment  ·  JavaScripting  ·  Admin →
    How important is this to you?

  17. More notifiers for live effects

    Ai provides a live effect notifier that triggers when an object is scaled, but not when it’s moved. Same problem with rotating — the absence of these does not allow to recalculate effects properly, like one when an object with a shadow is rotated, and a user wants to rotate the shadow with the object (there is a quite popular request about this one already — https://illustrator.uservoice.com/forums/333657-illustrator-desktop-feature-requests/suggestions/32468149-effects-do-not-rotate-drop-shadow-or-scale-e-g)

    9 votes
    0 comments  ·  C++ SDK  ·  Admin →
    How important is this to you?

  18. An Illustrator error occurred: 1346458189 ('PARM')

    I get this error too often on an irregular basis.
    Do something.
    At the very least, please return the correct cause of the error as to what caused the error.

    createOutline (),
    Move () for each object

    Etc., this error of the title is occurring too much during loop processing with for or while.
    I've come to hate Illustrator anymore.
    Please give the correct information to this error.
    I want to deal with it.

    This error has been the same since at least Illustrator CC 2014.
    I thought that the frequency of errors occurred in Illustrator CC 2017 was considerably…

    20 votes
    7 comments  ·  JavaScripting  ·  Admin →
    How important is this to you?
    Under Review  ·  AdminEgor Chistyakov (Admin, Adobe Illustrator) responded

    The team has made fixes related to this problem.

    Many script commands that were causing this error now won’t trigger it. Two commands though, Last Filter and Apply Last Filter would still give error because they are not exposed on UI as well.

  19. ExportOptionsJPEG both resolution and quality

    We can export a JPEG using ExportOptionsJPEG() — but it allows to set only quality, not a resolution.

    We can use ImageCaptureOptions() instead to set a resolution — but it won’t allow to set a quality, because seems to be designed for PNG (and substituting a format to JPG gives questionable results).

    We need to be able to export JPEG images, controlling both quality and resolution, without using app.doScript() trick — it fails on Cyrillic folder names.

    16 votes
    2 comments  ·  JavaScripting  ·  Admin →
    How important is this to you?

  20. ファイル名に#が付いた配置画像のファイルパスをapplescriptで得ようとすると問題あり

    例えばファイル名「ABC#123.psd」とした画像を配置し、
    選択したうえで

    tell application "Adobe Illustrator"
    get file path of selection
    end tell

    を実行するとリザルトが
    file "○○○:○○○:ABC"
    となり、#とそれ以降が無くなっている。
    正常ならば
    file "○○○:○○○:ABC#123.psd"
    となるはず。

    ファイル名に限らず、パス内に#が入っているとダメ。

    cs6、cc2018、cc2019では問題ない。
    cc2020(24.1.3)(24.2.1)(24.3.0)cc2021(25.2.3)パブリックベータは問題あり。

    macmini2018 macOS 10.14.6
    imac2020 macOS 11.2.3

    1 vote
    0 comments  ·  AppleScript  ·  Admin →
    How important is this to you?
1 3 5 6 7
  • Don't see your idea?

Illustrator (Desktop) SDK/Scripting Issues

Categories

Feedback and Knowledge Base

(thinking…)