• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers

P: Moving objects with numeric values (on Transform) affects position on ALL updated layer comps

1 Vote
Explorer ,
Feb 13, 2018 Feb 13, 2018

Copy link to clipboard

Copied

When setting new numeric values to objects (during Transform), these objects' position is also affected in updated layer comps (that have updated Layer Comp Position TURNED-ON!). 

This happens automatically after re-positioning the objects with numeric values, without updating the layer comps. 

This DOES not happen when manually moving the objects with the arrow keys or the mouse.

Here's a video capture of the bug:
https://www.youtube.com/watch?v=JJGZ5f4tJUU

Please fix this - since this bug damages my workflow considerably.

Thank you.

Bug Acknowledged
TOPICS
macOS , Windows

Views

23

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Feb 20, 2018 Feb 20, 2018
Jaroslav, I couldn't find another report. Do you have a URL?

I can reproduce the behavior. That said, I'm not sure it's unintended. If you do the translation via transform, it's not really considered a move but a Transform (not in the History panel that the history state is "Transform" which could include simple translation or full-on transformations, the history state without transform is simply "Move")

I've asked engineering to take a look.

Votes

Translate

Translate
4 Comments
LEGEND ,
Feb 13, 2018 Feb 13, 2018

Copy link to clipboard

Copied

Yes I know this bug since CS5. I think this was already reported.

Votes

Translate

Translate

Report

Report
Explorer ,
Feb 20, 2018 Feb 20, 2018

Copy link to clipboard

Copied

Can someone from Adobe address this?
Is this a known issue to you and are you going to fix it?

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Feb 20, 2018 Feb 20, 2018

Copy link to clipboard

Copied

Jaroslav, I couldn't find another report. Do you have a URL?

I can reproduce the behavior. That said, I'm not sure it's unintended. If you do the translation via transform, it's not really considered a move but a Transform (not in the History panel that the history state is "Transform" which could include simple translation or full-on transformations, the history state without transform is simply "Move")

I've asked engineering to take a look.

Senior Product Manager - Customer Advocacy - Digital Imaging

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 21, 2018 Feb 21, 2018

Copy link to clipboard

Copied

LATEST

Votes

Translate

Translate

Report

Report