Skip to content

Colin

My feedback

4 results found

  1. 58 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)
    Colin supported this idea  · 
  2. 187 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)
    Colin supported this idea  · 
  3. 724 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.

    Colin 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 – 23.0.6 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
    Colin commented  · 

    I'm getting the same thing.

    Any panels on the second monitor will jump from my "first" monitor (labeled "1" in Windows Display settings, connected via HDMI) to the "second" monitor (labeled "2" in Windows Display settings, connected via VGA). It does this when changing focus to/from fill or stroke, on both the tools panel and the color panel.

    I was using a workspace carried over from Illustrator 22, and this started happening right after updating to 23.0, and was still present in 23.0.1.

    I wasn't able to determine which/if any specific panel was causing it , but recreating my workspace from scratch seems to have stopped it from happening.

    Windows 10
    Illustrator 23.0.1
    Intel HD 4600 GPU, one monitor on HDMI, one monitor on VGA.

    Colin supported this idea  · 

Feedback and Knowledge Base