Skip to content
This repository has been archived by the owner on Dec 19, 2017. It is now read-only.

Entering negative transform value for LLSO (and other layers, i.e. Type) results in badness #3153

Closed
chadrolfs opened this issue Oct 28, 2015 · 10 comments

Comments

@chadrolfs
Copy link
Contributor

cmd/ctrl + n
drag a library asset onto canvas
click in Transform field (W) and enter a negative number (-50), Enter

Result: all fields are now blank. If you click on Layer 1 you'll error
Action transform.setSize failed: Error: Photoshop returned an error when playing command number: 2 Photoshop code: -1 Photoshop message: error: -1 message: Could not complete the command because the initial bounding rectangle is empty.

@chadrolfs
Copy link
Contributor Author

screen shot 2015-10-28 at 9 53 42 am

@chadrolfs
Copy link
Contributor Author

screen shot 2015-10-28 at 9 57 37 am

@shaoshing shaoshing self-assigned this Oct 28, 2015
@shaoshing
Copy link
Contributor

This is probably a core issue. The valid range for size is 0.1 ~ 32000 in DS. However, if we set the width / height less than 0.5 for some graphics (for example, Test - OK > Climber), they will turn into invisble with null w/h/x/y.

@shaoshing
Copy link
Contributor

@ktaki
Copy link
Contributor

ktaki commented Jan 14, 2016

This issue still exists, and the issue can be reproduced with any text layers (but no errors in console for text layer case). See the #3526.

@chadrolfs chadrolfs changed the title Entering negative transform value for LLSO results in badness Entering negative transform value for LLSO (and other layers, i.e. Type) results in badness Jan 14, 2016
@ktaki
Copy link
Contributor

ktaki commented Jan 14, 2016

Opened a bug in JIRA. https://jira.corp.adobe.com/browse/PS-884

@chadrolfs chadrolfs assigned iwehrman and unassigned chadrolfs Feb 19, 2016
@chadrolfs
Copy link
Contributor Author

I'm still able to hit this:

negxformvalues

@chadrolfs
Copy link
Contributor Author

using pgdev.1081 w/master @ 58fc655

@iwehrman
Copy link
Contributor

Isn't this the different bug that has to do with proportional locking? See #3725.

@iwehrman iwehrman assigned chadrolfs and unassigned iwehrman Feb 19, 2016
@chadrolfs
Copy link
Contributor Author

Oh right, my bad. As written, this is fixed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants