83 results found

1. Applescript "open without dialogs" no longer works

   I have an Applescript that has the statement

   open (thePDFName as alias) without dialogs

   In Adobe Illustrator 2019, it works. In Adobe Illustrator 2020, it gives me an "unable to open file" error. When I comment out "without dialogs", it opens the file, but then naturally pops open a dialog (not helpful when you are opening dozens of files!)

   MacOS 10.13.6, not sure what other information would be needed.

   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  ·  SDK and 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
   Under Review  ·  AdminRama (Mgr, Software Development, Adobe Illustrator) responded

   This issue is reproducible with HFS paths.

   Workaround: Use the POSIX path for opening files

   Example:
   set myFilePath to POSIX path of theAIFile
   open file myFilePath without dialogs

2. Fix Adobe Illustrator CC 2019 Type Library Reference - VB scripts return error

   Illustrator CC 2019 Type Library is broken when attempting to Reference from Visual Studio.

   VB.Net or C# projects attempt to add the reference from: C:\Program Files\Adobe\Adobe Illustrator CC 2019\Plug-ins\Extensions\Scripting Support.aip, and give the attached error.

   My idea, is for Adobe to fix it!

   Older versions work fine.

   •  

   • 

   37 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

   22 comments  ·  SDK and 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
   Completed (Comments Open)  ·  Ashutosh Chaturvedi responded

   We have the fix available in the latest release. Please update Illustrator using Adobe Creative Cloud application to the latest build for version Illustrator CC 23.0.2
   Please refer to our knowledge base FAQ – https://illustrator.uservoice.com/knowledgebase/articles/1844590 if you face difficulty in update.
   Or get in touch with us at any of the other support channels – https://helpx.adobe.com/support.html

   Warm Regards,
   Ashutosh Chaturvedi | Sr. Quality Engineering Manager – Illustrator
   Adobe. Make It an Experience.

3. ActiveX component can't create object: 'Illustrator.Application'

   We recently upgraded to CC 2019. version 23.0.6.

   Vbscripts are now unable to execute. They fail on:

   Set appRef = CreateObject('Illustrator.Application')

   with the error: ActiveX component can't create object: 'Illustrator.Application'

   This functionality is important to our workflow.

   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  ·  SDK and Scripting  ·  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. textFonts not refreshed after add/remove fonts. textFonts.getByName(fontName) doesn't throw error if font is not installed on user system.

   textFonts not refreshed after add/remove fonts. textFonts.getByName(fontName) doesn't throw error if font is not installed on user system.

   Code:
   for (var i = 0; i < usedFonts.length; i++) {
   try {
   var textFont= app.textFonts.getByName(usedFonts[i]);
   } catch (error) {
   missingFonts.push(usedFonts[i]);
   }
   }

   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  ·  SDK and Scripting  ·  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. scriptui

   Hello.

   On windows 7 and 10 (reproduced on my machine and a colleagues), when OS text scaling is higher than 100%, the dropdownLists in scriptUI don't work correctly.

   See attached, the horizontal and vertical scaling of the dropdown is smaller than the text it's meant to display, leading to options not being shown.

   It looks like the UI is being scaled after the dimensions are calculated, and the dropdown is just not updated at all (vertically or horizontally).

   This is a bit of an issue because our design team recently got high DPI monitors and they're having to disable UI scaling in illustrator as a workaround but it makes the entire UI tiny.

   I've attached a sample script and how screencaps of what they look on my machine (illustrator CS2019, windows 7)

   Hello.

   On windows 7 and 10 (reproduced on my machine and a colleagues), when OS text scaling is higher than 100%, the dropdownLists in scriptUI don't work correctly.

   See attached, the horizontal and vertical scaling of the dropdown is smaller than the text it's meant to display, leading to options not being shown.

   It looks like the UI is being scaled after the dimensions are calculated, and the dropdown is just not updated at all (vertically or horizontally).

   This is a bit of an issue because our design team recently got high DPI monitors and they're having to disable UI… 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  ·  SDK and 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

6. ExtendscriptToolkit is 32bit-only, OSX Catalina is 64bit-only

   I use a script I wrote for an important business function. For the last couple OSX upgrades, it has been warning me that ExtendscriptToolkit is not compatible with future versions of the OS. Specifically, OSX Catalina, which has been seeded to developers, will only support 64bit applications, and ExtendscriptToolkit is a 32bit application. Is that going to be addressed before the OS is released?

   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

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

7. Javascript textFonts.getByName() throws Illustrator error 1430996551

   Trying to use Javascript textFonts.getByName() throws Illustrator error 1430996551. Stopped working on some machines out of the blue, without any Illustrator update. Still works on at least one mac in the studio (same Illustrator version as on other computers).

   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  ·  SDK and Scripting  ·  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. extension do not work

   Illustrator 23.0.2 does not show extensions content even Adobe sample extensions like UI.

   I do not have any problem with other CC apps like Photoshop. Photoshop loads a shows the same UI extension.

   •  

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

9. Illustrator CC 2018 - CEP 8 HTML Extension Resize Issue

   We are experiencing resizing issue in the latest CEP version. Our extension allows user to resize extension's window, however whenever any navigation occur, window size resets. Problem exists in Illustrator CC 2018 (22.0.1), everything is working fine in previous version (CC 2017).
   We already tried different geometry settings and extension UI types, but problem persists and seems to be related to engine itself.

   We successfully reproduced this issue with official git hub sample extension. Steps to reproduce:
   1. Open sample extension with debug mode enabled
   2. Resize window
   3. Change window location in console to any other page
   4. After navigation, extension window size will reset

   For now, the only working workaround we've got is to save window size and resize it after each request. However, this solution isn't very elegant as window still moves it's position to default one.

   We are experiencing resizing issue in the latest CEP version. Our extension allows user to resize extension's window, however whenever any navigation occur, window size resets. Problem exists in Illustrator CC 2018 (22.0.1), everything is working fine in previous version (CC 2017).
   We already tried different geometry settings and extension UI types, but problem persists and seems to be related to engine itself.

   We successfully reproduced this issue with official git hub sample extension. Steps to reproduce:
   1. Open sample extension with debug mode enabled
   2. Resize window
   3. Change window location in console to any other page
   4. After… 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

   2 comments  ·  SDK and 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
   Completed (Comments Open)  ·  Ashutosh Chaturvedi responded

   We have the fix available in the latest release. Please update Illustrator using Adobe Creative Cloud application to the latest build for version Illustrator CC 23.0.
   Please refer to our knowledge base FAQ – https://illustrator.uservoice.com/knowledgebase/articles/1844590 if you face difficulty in update.
   Or get in touch with us at any of the other support channels – https://helpx.adobe.com/support.html

   Warm Regards,
   Ashutosh Chaturvedi | Sr. Quality Engineering Manager – Illustrator
   Adobe. Make It an Experience.

10. Actions based on Scripts not saving after restart?

    From: https://forums.adobe.com/thread/2191151

    I located another thread from December where the consensus seems to be that this is a long standing and known bug with Illustrator.
    Permanently saving scripts in Action Set doesn't work / Scripts werden nicht dauerhaft in den Aktionseinstellungen gespeichert.

    I have spent a good deal of time working with people here on the Adobe forums to develop a script to automate a very large function of my job, and now that it is completed it should be ready to pass on to members of my team so they can utilize it as well. The problem is that even though the scripts are loaded into the proper scripts folder and the Action works for running a batch off that script flawlessly, it disappears every time Illustrator restarts.

    Is this really a permanent bug with Illustrator? Is Adobe really just ignoring this problem?

    For those unaware, here is a screenshot to help demonstrate:
    thumbnail_Screen Shot 2016-08-04 at 12.04.15 PM.png

    I have created my own folder for custom actions. In that folder I have created an action titled "CAD Batching Script [Network]". I then followed standard procedure, recorded the action, told it to "Insert a Menu Item" and then selected the appropriate script from the Scripts menu under File. Hit stop on the recording, done.

    I'm then able to run the action off of the Batch function and everything works flawlessly.

    Then, the next time I re-open Illustrator after closing the program, the recorded parts of the action (highlighted in the red box in the screenshot) have totally disappeared. I tested this both in my custom folder and by placing the action in the Default Actions folder. Nothing seems to keep it from disappearing.

    Is there something I'm missing, or am I just forever out of luck and going to have to recreate the Action every time I open Illustrator and need to work off of that script for batch processing?

    Thanks in advance,
    Brooks

    From: https://forums.adobe.com/thread/2191151

    I located another thread from December where the consensus seems to be that this is a long standing and known bug with Illustrator.
    Permanently saving scripts in Action Set doesn't work / Scripts werden nicht dauerhaft in den Aktionseinstellungen gespeichert.

    I have spent a good deal of time working with people here on the Adobe forums to develop a script to automate a very large function of my job, and now that it is completed it should be ready to pass on to members of my team so they can utilize it as well. The problem is that… more

    13 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

    17 comments  ·  SDK and 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
    Completed (Comments Open)  ·  AdminIllustrator Engineering (Software Engineer, Adobe Illustrator) responded

    I am happy to share that we have fixed this bug in our latest release – 26.4.1 which is available worldwide now.

    You can update to the latest release using Creative Cloud desktop App: https://helpx.adobe.com/in/creative-cloud/help/creative-cloud-updates.html

    Thank you for all the feedback. Keep it coming!

    Regards,

    Rohit Jain

    Illustrator Team

11. Flaws in AI CC Actions

    Hi,

    I'm recording Actions to in Illustrator CC 2018 ( 22.1) and I've found a few things lacking:

    1) When I group objects, and name the group, while recording an action the name does not get recorded.

    The group just bears the name "group".

    2) If you choose "Expand" while recording an action and choose from the available options (Fill, Stroke, etc), you are asked to make that choice again when the action runs- not much of an Action! .

    Aside from the above I find the lack of Conditional Action, as per Photoshop, features disappointing.

    Are there any fixes for the above flaws or is my version of Illustrator not behaving as expected?

    I just don't know.

    Thanks

    Hi,

    I'm recording Actions to in Illustrator CC 2018 ( 22.1) and I've found a few things lacking:

    1) When I group objects, and name the group, while recording an action the name does not get recorded.

    The group just bears the name "group".

    2) If you choose "Expand" while recording an action and choose from the available options (Fill, Stroke, etc), you are asked to make that choice again when the action runs- not much of an Action! .

    Aside from the above I find the lack of Conditional Action, as per Photoshop, features disappointing.

    Are there any fixes… 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  ·  SDK and 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

12. Playing scripts via action with no open documents

    Running scripts via an action only appears to work if there is at least one open document.

    Steps:
    1. Create a simple script (such as app.documents.add)
    2. Save to Illustrator scripts folder.
    3. Record to action via 'Insert Menu Item'
    4. Make sure no documents are open
    5. Play action. Illustrator displays the message 'The object <ScriptName> is not currently available.'

    If you run the script via File > Scripts, it runs normally. I don't think this should be expected behaviour; if the menu command runs the script, the action should too, regardless of whether or not there is an already open document.

    Running scripts via an action only appears to work if there is at least one open document.

    Steps:
    1. Create a simple script (such as app.documents.add)
    2. Save to Illustrator scripts folder.
    3. Record to action via 'Insert Menu Item'
    4. Make sure no documents are open
    5. Play action. Illustrator displays the message 'The object <ScriptName> is not currently available.'

    If you run the script via File > Scripts, it runs normally. I don't think this should be expected behaviour; if the menu command runs the script, the action should too, regardless of whether or not there is an… 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  ·  SDK and 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

13. Illustrator quits unexpectedly when my script run for long

    When I open Illustrator in my MacOS Sierra 10.12.5 and run my script, after 10-20 min Illustrator quits unexpectedly and this log shows up.

    Process: Adobe Illustrator [668]
    Path: /Applications/Adobe Illustrator CC 2018/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator
    Identifier: com.adobe.illustrator
    Version: 22.0.1 (22.0.1)
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: Adobe Illustrator [668]
    User ID: 501

    Date/Time: 2018-03-22 11:55:00.252 +0400
    OS Version: Mac OS X 10.12.5 (16F2073)
    Report Version: 12
    Anonymous UUID: 275016EB-9652-BDEE-B228-38BD1F63F6C7

    Time Awake Since Boot: 5800 seconds

    System Integrity Protection: enabled

    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Exception Type: EXCCRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Exception Note: EXCCORPSE_NOTIFY

    Application Specific Information:
    terminating with uncaught exception of type CAIAPIFault: std::exception
    abort() called

    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0 libsystemkernel.dylib 0x00007fffd5e37d42 _pthreadkill + 10
    1 libsystempthread.dylib 0x00007fffd5f25457 pthreadkill + 90
    2 libsystemc.dylib 0x00007fffd5d9d420 abort + 129
    3 libc++abi.dylib 0x00007fffd48f384a abortmessage + 266
    4 libc++abi.dylib 0x00007fffd4918c37 defaultterminatehandler() + 243
    5 libobjc.A.dylib 0x00007fffd5426713 _objcterminate() + 124
    6 libc++abi.dylib 0x00007fffd4915d69 std::__terminate(void (*)()) + 8
    7 libc++abi.dylib 0x00007fffd4915de3 std::terminate() + 51
    8 com.adobe.illustrator 0x000000010023db4d 0x100000000 + 2349901
    9 com.adobe.illustrator 0x00000001002397d2 0x100000000 + 2332626
    10 com.adobe.illustrator 0x00000001008938d5 0x100000000 + 8992981
    11 com.adobe.illustrator 0x000000010088eb45 0x100000000 + 8973125
    12 com.adobe.illustrator 0x0000000100cd4ec1 0x100000000 + 13455041
    13 com.adobe.illustrator 0x0000000100ccf023 0x100000000 + 13430819
    14 com.adobe.illustrator 0x0000000100cd2614 0x100000000 + 13444628
    15 com.adobe.illustrator 0x00000001009fb860 0x100000000 + 10467424
    16 com.adobe.illustrator 0x00000001009f9f5f 0x100000000 + 10461023
    17 com.adobe.illustrator 0x000000010025698b 0x100000000 + 2451851
    18 com.adobe.illustrator 0x00000001001cd0c7 0x100000000 + 1888455
    19 com.adobe.illustrator.plugins.ActionPalette 0x0000000124d9e902 0x124d86000 + 100610
    20 com.adobe.illustrator.plugins.ActionPalette 0x0000000124da5bd2 0x124d86000 + 130002
    21 com.adobe.illustrator.plugins.ActionPalette 0x0000000124dc9cad 0x124d86000 + 277677
    22 com.adobe.illustrator.plugins.Action 0x00000001137f5b52 0x1137f2000 + 15186
    23 com.adobe.illustrator.plugins.ScriptingSupport 0x000000011b21ca20 PluginMain + 266096
    24 com.adobe.illustrator.plugins.ScriptingSupport 0x000000011b21601c PluginMain + 238956
    25 com.adobe.illustrator.plugins.ScriptingSupport 0x000000011b216b73 PluginMain + 241859
    26 com.adobe.illustrator.plugins.ScriptingSupport 0x000000011b293ab8 PluginMain + 753672
    27 com.adobe.illustrator.plugins.ScriptingSupport 0x000000011b2dd5a8 PluginMain + 1055480
    28 com.adobe.AdobeExtendScript 0x0000000108a78e4d ScScript::LiveObjectFunction::propCall(ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&) + 413
    29 com.adobe.AdobeExtendScript 0x0000000108a0a0ad jsOpCall::run(jsRunner&, ScScript::ESVariant&) const + 877
    30 com.adobe.AdobeExtendScript 0x0000000108a12462 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 146
    31 com.adobe.AdobeExtendScript 0x0000000108a0d5b3 jsOpIf::run(jsRunner&, ScScript::ESVariant&) const + 211
    32 com.adobe.AdobeExtendScript 0x0000000108a12462 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 146
    33 com.adobe.AdobeExtendScript 0x0000000108a0d5b3 jsOpIf::run(jsRunner&, ScScript::ESVariant&) const + 211
    34 com.adobe.AdobeExtendScript 0x0000000108a12462 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 146
    35 com.adobe.AdobeExtendScript 0x0000000108a0c662 jsOpFunction::run(jsRunner&, ScScript::ESVariant&) const + 418
    36 com.adobe.AdobeExtendScript 0x0000000108a39805 jsRunner::run(ScScript::ESVariant&) + 117
    37 com.adobe.AdobeExtendScript 0x0000000108a242bb jsFunction::propCall(ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&) + 155
    38 com.adobe.AdobeExtendScript 0x0000000108a0a0ad jsOpCall::run(jsRunner&, ScScript::ESVariant&) const + 877
    39 com.adobe.AdobeExtendScript 0x0000000108a12462 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 146
    40 com.adobe.AdobeExtendScript 0x0000000108a0d5b3 jsOpIf::run(jsRunner&, ScScript::ESVariant&) const + 211
    41 com.adobe.AdobeExtendScript 0x0000000108a12462 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 146
    42 com.adobe.AdobeExtendScript 0x0000000108a0c662 jsOpFunction::run(jsRunner&, ScScript::ESVariant&) const + 418
    43 com.adobe.AdobeExtendScript 0x0000000108a39805 jsRunner::run(ScScript::ESVariant&) + 117
    44 com.adobe.AdobeExtendScript 0x0000000108a242bb jsFunction::propCall(ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&) + 155
    45 com.adobe.AdobeExtendScript 0x0000000108a0a0ad jsOpCall::run(jsRunner&, ScScript::ESVariant&) const + 877
    46 com.adobe.AdobeExtendScript 0x0000000108a12462 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 146
    47 com.adobe.AdobeExtendScript 0x0000000108a1121e jsOpSimpleFor::run(jsRunner&, ScScript::ESVariant&) const + 654
    48 com.adobe.AdobeExtendScript 0x0000000108a12462 jsOpStatements::run(jsRunner&, ScScript::ESVariant&) const + 146
    49 com.adobe.AdobeExtendScript 0x0000000108a0c662 jsOpFunction::run(jsRunner&, ScScript::ESVariant&) const + 418
    50 com.adobe.AdobeExtendScript 0x0000000108a39805 jsRunner::run(ScScript::ESVariant&) + 117
    51 com.adobe.AdobeExtendScript 0x0000000108a24395 jsFunction::propCall(ScScript::Object&, ScCore::BasicArray const&, ScScript::ESVariant&) + 373
    .....

    When I open Illustrator in my MacOS Sierra 10.12.5 and run my script, after 10-20 min Illustrator quits unexpectedly and this log shows up.

    Process: Adobe Illustrator [668]
    Path: /Applications/Adobe Illustrator CC 2018/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator
    Identifier: com.adobe.illustrator
    Version: 22.0.1 (22.0.1)
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: Adobe Illustrator [668]
    User ID: 501

    Date/Time: 2018-03-22 11:55:00.252 +0400
    OS Version: Mac OS X 10.12.5 (16F2073)
    Report Version: 12
    Anonymous UUID: 275016EB-9652-BDEE-B228-38BD1F63F6C7

    Time Awake Since Boot: 5800 seconds

    System Integrity Protection: enabled

    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Exception Type: EXCCRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Exception Note: EXC… 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

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

14. IllustratorSaveOptions in C# .NET is not working anymore as expected

    For more than a decade the following Illustrator script has been applied via C# .NET in combination with all existing Illustrator versions (sourcecode):

    typelib.IllustratorSaveOptions saveOptions = new typelib.IllustratorSaveOptions();
    saveOptions.Compatibility = typelib.AiCompatibility.aiIllustrator8;
    saveOptions.FlattenOutput = typelib.AiOutputFlattening.aiPreserveAppearance;
    DestDoc.SaveAs(sPath, saveOptions);

    All over the internet we see a lot of people using the same code above (applying the exact same idea) also in other programming languages.

    Following test has been done with Illustrator versions CS, CS2, CS3, CS5, CS6, etc. on the latest Windows 10 operating system and VS2012: draw 2 intersecting rectangles: above yellow, the other red. A transparency Difference has been set on the yellow rectangle.

    AI version 8.0 output results via scripted AI 8.0 output:
    using the source code above, in versions up to and CS5, three rectangles are outputted (transparency is being flattened), but later versions (CS6 up to and the latest Creative Cloud Illustrator version) outputs only two rectangles (do not flatten but remove the transparency as if option aiPreservePaths instead of aiPreserveAppearance is active).

    Everything is working well in case the save to AI format 8.0 is done manually from within the Illustrator programs.

    What has been changed that has broken this functionality? Do we have to add something to the code mentioned above, or, has a bug been introduced in Illustrator from version CS5 to CS6 which is still present up to and today? We have no idea why this is not working anymore. Please look into it because this piece of functionality is quite important for our customers.

    For more than a decade the following Illustrator script has been applied via C# .NET in combination with all existing Illustrator versions (sourcecode):

    typelib.IllustratorSaveOptions saveOptions = new typelib.IllustratorSaveOptions();
    saveOptions.Compatibility = typelib.AiCompatibility.aiIllustrator8;
    saveOptions.FlattenOutput = typelib.AiOutputFlattening.aiPreserveAppearance;
    DestDoc.SaveAs(sPath, saveOptions);

    All over the internet we see a lot of people using the same code above (applying the exact same idea) also in other programming languages.

    Following test has been done with Illustrator versions CS, CS2, CS3, CS5, CS6, etc. on the latest Windows 10 operating system and VS2012: draw 2 intersecting rectangles: above yellow, the other red. A transparency Difference has been set on… 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

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

15. javascript doc.close() after error

    https://forums.adobe.com/message/9853322#9853322
    for details

    When you close the file in the script
    After that, an error (1346458189 ('PARM')) occurs with high probability.
    Closed processing is closed up to what is not closed or can not be closed
    It looks like a bug.

    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

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

16. Failure to create artboards when reading file with SDK in CC 2018

    Issue occurs in CC 2018 when creating artboards during the GoFileFormat message handler in a plugin that registers its own file format.

    In previous versions you could create artboards up to the size of the canvas using AIArtboard::SetPosition without any errors. In CC 2018 when you call AIArtboard::SetPosition it seems to compare the position to the result of AIDocument::GetDocumentMaxArtboardBounds and if it is outside of the maximum bounds it returns an error code. In CC 2018, the maximum art boards for a new document seem to be based on the /artboard setting in the preferences file, which in turn seems to be based on the documents the user has been working with.

    This means that if you have two users, one who uses small documents and one who uses large documents and they both open the same medium size file using your plugin, it works for the user who has been using large documents but not for the user who has been using small documents. As there is no AIDocument::SetDocumentMaxArtboardBounds function, there seems to be no way the plugin can overcome this issue.

    Issue occurs in CC 2018 when creating artboards during the GoFileFormat message handler in a plugin that registers its own file format.

    In previous versions you could create artboards up to the size of the canvas using AIArtboard::SetPosition without any errors. In CC 2018 when you call AIArtboard::SetPosition it seems to compare the position to the result of AIDocument::GetDocumentMaxArtboardBounds and if it is outside of the maximum bounds it returns an error code. In CC 2018, the maximum art boards for a new document seem to be based on the /artboard setting in the preferences file, which in turn seems… 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

    10 comments  ·  SDK and 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

17. GetPresetSettings function doesn't work correctly in CC 2017 and later

    In Illustrator CC 2017 (22.x) and CC 2018 (23.x) the AIDocumentList::GetPresetSettings function is broken. It still returns an error if the preset doesn't exist, but if the preset does exist, it returns 0, but doesn't fill in the AINewDocumentPreset structure.

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

18. Properties of Placed Illustrator file

    I have a illustrator design file, I could able to place the file in another Illustrator design document, but when I read the properties of the placed object the "name" value shows empty.

    Consider this as a bug and fix in future release

    •  

    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  ·  SDK and Scripting  ·  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. kAIXMLNameChangedNotifier behaviour change

    The following code worked perfectly in 2015, 2015.1, 2017 but in 2018 it broke.

    My notifier is created like so :
    error = sAINotifier->AddNotifier(fPluginRef, kCinewarePluginName, kAIXMLNameChangedNotifier, &fUIDChangeNotifier);

    It is correctly triggered on the renaming of an art element. This then calls the following code :

    ASErr ArtSelectionRenamedNotifier(AINotifierMessage message)
    {
    ASErr error = kNoErr;
    fprintf(stderr,"ArtSelectionRenamedNotifier\n");
    //First get the AiArtHandle
    AIPluginGroupMessage myMessage = (AIPluginGroupMessage*)message;
    fprintf(stderr,"ArtSelectionRenamedNotifier msg type[%s]\n",message->type);
    //The relabelled art
    AIArtHandle relabelledArt = myMessage->preEditArt;
    fprintf(stderr,"ArtSelectionRenamedNotifier msg preEditArt[%p] is valid Art?[%s]\n",relabelledArt,sAIArt->ValidArt(relabelledArt, true)?"YES":"NO");
    //Verify it has a UID
    ai::UnicodeString relabelledArtUUID;
    //The artUIDName will be empty if not yet made
    if (relabelledArt)
    {
    error = sAIUIDUtils->GetArtUIDName(relabelledArt, relabelledArtUUID);
    }
    fprintf(stderr,"ArtSelectionRenamedNotifier msg preEditArt[%p] UUID[%s]\n",relabelledArt,relabelledArtUUID.asUTF8().cstr());

    The above code works perfectly in 2017, 2015 and 2015.3 :
    ArtSelectionRenamedNotifier
    ArtSelectionRenamedNotifier msg type[AI XML Name Changed Notifier]
    ArtSelectionRenamedNotifier msg preEditArt[0x157287b80] is valid Art?[YES]
    ArtSelectionRenamedNotifier msg preEditArt[0x157287b80] UUID[Green]

    Then in 2018 and (22.0 and 22.1) :
    ArtSelectionRenamedNotifier
    ArtSelectionRenamedNotifier msg type[AI XML Name Changed Notifier]
    ArtSelectionRenamedNotifier msg preEditArt[0x10003e501] is valid Art?[NO]
    Segmentation fault

    The seg fault occurs inside the GetArtUIDName, no doubt as the art in invalid.

    If this is intentional behaviour, can it be detailed how to get the arthandle that has changed?

    Kind Regards,
    R

    The following code worked perfectly in 2015, 2015.1, 2017 but in 2018 it broke.

    My notifier is created like so :
    error = sAINotifier->AddNotifier(fPluginRef, kCinewarePluginName, kAIXMLNameChangedNotifier, &fUIDChangeNotifier);

    It is correctly triggered on the renaming of an art element. This then calls the following code :

    ASErr ArtSelectionRenamedNotifier(AINotifierMessage message)
    {
    ASErr error = kNoErr;
    fprintf(stderr,"ArtSelectionRenamedNotifier\n");
    //First get the AiArtHandle
    AIPluginGroupMessage myMessage = (AIPluginGroupMessage*)message;
    fprintf(stderr,"ArtSelectionRenamedNotifier msg type[%s]\n",message->type);
    //The relabelled art
    AIArtHandle relabelledArt = myMessage->preEditArt;
    fprintf(stderr,"ArtSelectionRenamedNotifier msg preEditArt[%p] is valid Art?[%s]\n",relabelledArt,sAIArt->ValidArt(relabelledArt, true)?"YES":"NO");
    //Verify it has a UID
    ai::UnicodeString relabelledArtUUID;
    //The artUIDName will be empty if not yet made
    if (relabelledArt)
    {
    error =… 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  ·  SDK and Scripting  ·  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. Possible bug: Crash after script runs... runs OK in ESTK.

    I believe this might be a bug since it crashed Illustrator rather than the script crashing gracefuly.

    I have a script which, when completed, crashes Illustrator. The script runs fine when ran from within the ESTK but crashes when ran from the AI File->Scripts menu. Attached is the crash log. I cannot post the script itself here but am willing to send it to an Adobe employee privately if needed.

    • 

    • 

    • 

    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  ·  SDK and 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
    Under Review  ·  AdminIllustrator Engineering (Software Engineer, Adobe Illustrator) responded

    Thanks for sharing the script, we are able to repro the issue at our side & have forwarded it to the engineering team for further isolation.

    With Best Regards,
    Raghuveer