Skip to content

Kevin A.

My feedback

21 results found

  1. 50 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Kevin A. supported this idea  · 
  2. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Kevin A. supported this idea  · 
  3. 31 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Kevin A. supported this idea  · 
  4. 11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

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

    Going forward, our goal is to fix as many top User-Voice bugs as possible and as frequently as possible. Given the nature of the fixes, some of the bugs will take a longer time to fix, but we are on it.

    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!

    An error occurred while saving the comment
    Kevin A. commented  · 

    We are experiencing the same problem, and, in fact it even seems like Wacom know about this problem themselves:
    https://support.wacom.com/hc/en-us/articles/4412354516247-Why-is-pressure-not-working-in-Adobe-Illustrator-on-macOS-

    "Note: There is an issue with Adobe Illustrator 2021 that does not allow you to make the above selection in the system preferences. To resolve this issue you will need to uninstall the Wacom Driver and Adobe Illustrator, then reinstall the Wacom driver (following the steps from step 1) and then install the older 2020 version of Illustrator. If this version does not appear on the Creative Cloud application list, please reach out to Adobe Support."

    We have also tested the latest edition of Illustrator (26.0.2 at time of writing) and that still does not solve this issue. I am positive this is an Illustrator-specific problem because even Photoshop works fine with pen pressure settings out of the box.

    Kevin A. supported this idea  · 
  5. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Kevin A. commented  · 

    Same problem for us on:
    - macOS Catalina (10.15.7)
    - Big Sur (11.5.2)
    - Illustrator (25.4.1)

    Pressing other keys in the brief period before the save dialog is shown will reliably produce this "The save operation failed to connect to the open and save panel service" error message. For example, choose "Save As" and quickly hit the right arrow key twice in succession.

    This is causing headaches for some of the faster folks in our team.

    Kevin A. supported this idea  · 
  6. 21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Kevin A. commented  · 

    Glad to hear this is being looked at! We also stumbled into this issue on 25.4.1. We use the XMP library to embed some extra data in PDFs so it's a critical component for us.

    I was able to work around it by importing the AdobeXMPScript framework from Illustrator 25.3.1. Not sure how safe this is so YMMV, but figured I'd document it anyway:

    MacOS:
    - Uninstall Illustrator 2021
    - From the CC App's "Other Versions" list, install Illustrator 25.3.1
    - Open Applications/Adobe Illustrator 2021
    - Right-click on "Adobe Illustrator 2021.app" and choose "Show Package Contents"
    - Browse down to Contents/Frameworks
    - Copy the "AdobeXMPScript.framework" folder to your desktop
    - Update Illustrator back to 25.4.1
    - Open "Applications/Adobe Illustrator 2021" again
    - Right-Click on "Adobe Illustrator 2021.app" and choose "Show package contents" again
    - Browse down to Contents/Frameworks
    - Paste the "AdobeXMPScript.framework" folder from your desktop into this Contents/Frameworks folder
    - Restart Illustrator and try your script

    In my testing this is not an issue on the Windows build. Mac Only (as seems to be happening more frequently these days...)

    Kevin A. supported this idea  · 
  7. 146 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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 22.1.
    Please refer to our knowledge base FAQhttps://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.

    An error occurred while saving the comment
    Kevin A. commented  · 

    This problem resurfaced in Illustrator 2021. At time of writing I can reproduce it on the 25.2.1 build. I have not seen a response from an Adobe admin since 2018 -- perhaps we need to re-open this as a new issue?

    Kevin A. supported this idea  · 
  8. 32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

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

    Going forward, our goal is to fix as many top User-Voice bugs as possible and as frequently as possible. Given the nature of the fixes, some of the bugs will take a longer time to fix, but we are on it.

    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!

    An error occurred while saving the comment
    Kevin A. commented  · 

    Happening for us as well. We are clinging to Illustrator 2018 because bugs like this are unacceptable.

    Kevin A. supported this idea  · 
  9. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Kevin A. commented  · 

    Looks like this is still broken in Illustrator 2021.

    In case anyone else comes across this thread, here's the workaround I've started using for our internal scripts. The gist is that we can use ScriptUI to create a custom input dialog for the filename, then launch a folder selection dialog to set the save location. Not the best since it's two modals folks have to click through, but it's still faster than manually keying in file names.

    ```
    #target illustrator
    #targetengine "main"

    function setFileName(currentDocName) {
    var newName = currentDocName.split('.')[0];

    var fileNameInputWindow = new Window("dialog", "Save as...");
    var fileNameForm = fileNameInputWindow.add("group");
    fileNameForm.add("statictext", undefined, "Name:");
    var fileNameTextField = fileNameForm.add("edittext", undefined, newName);
    fileNameTextField.characters = 40;
    fileNameTextField.active = true;
    var confirmationButtons = fileNameInputWindow.add("group");
    confirmationButtons.alignment = "right";
    confirmationButtons.add("button", undefined, "Save", { name: "ok" });
    confirmationButtons.add("button", undefined, "Cancel");
    if (fileNameInputWindow.show() == 1) {
    return fileNameTextField.text;
    }
    }

    function setSaveLocation() {
    var parentDirectory = currentDocPath.toString();
    parentDirectory = parentDirectory.substr(0, parentDirectory.lastIndexOf('/')) + "/";
    parentDirectory = parentDirectory === '/' ? "~/" : parentDirectory;
    var newDestination = Folder.selectDialog('Choose Save Location...', parentDirectory);
    return newDestination;
    }

    function createSaveFile(docName, destination, extension) {
    var newName = '';
    if (docName.indexOf('.') < 0) {
    newName = docName + extension;
    } else {
    var dot = docName.lastIndexOf('.');
    newName += docname.substring(0, dot);
    newName += extension;
    }

    return new File(destination + '/' + newName);
    }

    function saveTheFile() {
    var doc = app.activeDocument;
    var extension = '.eps';

    var newDocName = setFileName(doc.name);
    if (!newDocName) { return };

    var newDocLocation = setFolderLocation(doc.fullName);
    if (!newDocLocation) { return };

    var savePath = createSaveFile(newDocName, newDocLocation, extension);
    var saveOptions = new EPSSaveOptions;
    saveOptions.compatibility = Compatibility.ILLUSTRATOR14;
    doc.saveAs(savePath, saveOptions);
    }

    saveTheFile();
    ```

    An error occurred while saving the comment
    Kevin A. commented  · 

    Hi there,

    I'm having some issues with a custom extendscript that we use in our production house. This script is pretty basic, and is meant to make eps / pdf / ai conversion easier (we have some strict EPS settings that must be followed). This script has worked on AiCC (original release) up through CC 2019, but is now behaving oddly in Illustrator 2020.

    When you run the script, a custom "Save As" dialog should show up. The filename should default to the current document's name, with .eps set as the filetype suffix. However, when running this script in Illustrator 2020, the filename field is ALWAYS defaulting to "Untitled.eps".

    I've attached two screenshots that show the difference in behavior. One that shows how this script's save dialog looks in Illustrator 2019 (correct), and one that shows how this script's save dialog looks in Illustrator 2020 (incorrect).

    It would be great if this was fixed. For reference, I have tested this code on MacOS Mojave 10.14.6 as well as MacOS Catalina 10.15.2. Both OS's result in the same behavior.

    It appears that this form does not let you attach .jsx files, but I can provide the source file if needed (it seems to be a problem with the saveDlg() method specifically). Here is a basic example to test, though:

    ```
    \#target illustrator
    \#targetengine "main"

    function saveTheFile() {
    var tmpFile = new File("~/Desktop/testFile.eps").saveDlg("Choose a save location:");
    if (tmpFile == null) return;

    var saveOpts = new EPSSaveOptions;
    saveOpts.compatibility = Compatibility.ILLUSTRATOR14;
    app.activeDocument.saveAs(tmpFile, saveOpts);
    }

    saveTheFile();

    Kevin A. shared this idea  · 
  10. 279 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi Everyone,

    We have fixed this bug in our latest release – v 24.2.1 which is available worldwide now. Thanks for your patience on this.

    Please note that after upgrading you might still see that Align To sets itself to Align to Key Object. If you see this, please manually set the Align To to the required setting, and this reported bug will not happen again. You’ll need to this one time only.

    The reason Align To might get set to Key Object after update is because Ai remembers your last Align To on subsequent launches as well. So, if your last Align To was Key Object before quitting/upgrading, after first multi-selection, it will set itself to Key Object. After you manually change it one-time, it will work fine.

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

    Kevin A. supported this idea  · 
  11. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Kevin A. commented  · 

    Our organization would like this feature as well. We maintain a set of marketing assets that are divided into a few different symbol libraries. Being able to search by asset names within each of these libraries would expedite our day-to-day processes quite a bit.

    I recognize this feature is offered by Adobe Libraries, but our workflow at the moment prohibits us from using that tool. As mentioned by the OP, this feature exists for swatch palettes, so it'd be nice to see the same functionality available to symbol palettes (and perhaps even others, like the Brush palette).

    Kevin A. supported this idea  · 
  12. 37 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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 FAQhttps://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.

    An error occurred while saving the comment
    Kevin A. commented  · 

    Also experiencing this problem after updating to Illustrator 2019 (23.0.1 64-bit) on my Windows 10 (build 17763) machine. Any VBScript simply fails to execute, returning an "Internal Script Execution Error" message. Makes no difference if I try to run the script via the File > Scripts menu, or via native execution from the OS file browser.

    The problem doesn't seem to affect the other creative cloud apps (for example, the snippet below works fine in PS, but not in AI):

    Illustrator --
    Set appRef = CreateObject("Illustrator.Application")
    appRef.Documents.Add()
    MsgBox("Document Created!")

    Photoshop --
    Set appRef = CreateObject("Photoshop.Application")
    appRef.Documents.Add()
    MsgBox("Document Created!")

    Kevin A. supported this idea  · 
  13. 35 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Kevin A. shared this idea  · 
  14. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Kevin A. supported this idea  · 
  15. 148 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Started  ·  Dirk Schulze responded

    Just a general status update. We are currently and will continuously improve SVG import support in Adobe Illustrator. We are currently working on solving the issues mentioned in this report. Please feel free to open new bug reports here on uservoice if you are experiencing additional/untracked issues.

    Kevin A. supported this idea  · 
  16. 707 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Kevin A. supported this idea  · 
  17. 717 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    It is not as straightforward as it may sound :) We have been working to take advantage of threads and other hardware such as GPU/Video RAM in places where it can make a higher impact. We are prioritizing areas that are slow instead of making a generic change and destabilizing the product. Product stability is the top priority for us and we have been consistently trying to improve it. We want to move with caution and make changes without compromising on the quality. Hope this helps.

    Kevin A. supported this idea  · 
  18. 385 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Kevin A. supported this idea  · 
  19. 94 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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 FAQhttps://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.

    An error occurred while saving the comment
    Kevin A. commented  · 

    We've been experiencing the same issue since Ai2015 on our 5k iMacs. Performance suffers so much that CPU Preview mode is essentially unusable, which is a shame because the artifacts and errors introduced by GPU mode have been a headache to deal with.

    Kevin A. supported this idea  · 
  20. 15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Kevin A. commented  · 

    I've been experiencing this same problem since the initial Ai2015 release. Seems to continue on in the latest builds for me as well.

    Kevin A. supported this idea  · 
← Previous 1

Feedback and Knowledge Base