Skip to content

Birger

My feedback

2 results found

  1. 46 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)
  2. 280 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

    An error occurred while saving the comment
    Birger commented  · 

    OK
    Was fixed when doing what's told...got my reading glasses on now .
    Changed the Align to option in the top bar located just to the left of the Align-possibilities

    An error occurred while saving the comment
    Birger commented  · 

    Align is not working - still...

    2 or more objects will not align to left
    2 or more will not align to top

    We were promised in a mail from Srishti Bali (Adobe Support Community) that this would be fixed in the version 24.2.1, but after updating to that version, this item was not fixed

Feedback and Knowledge Base