Skip to main content
Inspiring
October 15, 2018

P: Transform/Resize is constrained by default - Want ability to go back to legacy behavior

  • October 15, 2018
  • 778 replies
  • 23665 views

When selecting a layer and dragging a corner handle with the shift (or alt-shift) key pressed, the resize proportion isn't constrained. This started with this most recent update.

This topic has been closed for replies.

778 replies

Participant
March 8, 2019
I, too, have been using Photoshop forever, and the legacy behavior is etched into my brain. The change has been driving me crazy 🙂 I've reverted back to version 19.1.7 for now, but hoping future releases will be corrected back.

I called Adobe Customer Support and logged this complaint. The first rep offered me 15-day credit on my subscription. They then passed me through to the User Support to explain how the tool works (ha!) and I again logged the complaint. They offered a 2-month credit on my subscription. Perhaps if enough users ask for refunds as well as log complaints, Adobe will change PS Constrain Transform back to legacy behavior. 
David Mohr
Participating Frequently
March 8, 2019
Again, I'm happy to try to share your voices and input with the team, but it would be far more effective if you want your perspectives really heard to join the Photoshop prerelease program.  There are limits to what an employee of a publicly-traded company can discuss on a public forum with regard to a feature under development...

That said, it wasn't just one tool.  Many behaviors were changed.  That's why a fix isn't immediate.  We TRULY want to get this right for users, including all the many and sundry fringe cases.  And believe me, there are multiple (conflicting) consistency arguments involved...8-(

Thanks,
David
Legend
March 8, 2019
Thanks David, 

But the real problem isn't changing shift-to-constrain. The problem is changing it on one tool, in one app. 

That's like switching 1st gear with reverse but only for one road.

This huge UI/UX inconsistency, and the sheepish roll-out, raises a lot of questions because we're in an ongoing relationship with you.

We're getting a lot of 'you can't teach old dogs new tricks' attitude but that isn't the issue. 

It's about design consistency, and basic communication. Both were of shockingly low-quality in this instance, and these aspects are yet to be acknowledged by Adobe.

I hope that makes sense and thank you again for taking the time to post here.

Ben


 
donbarrum
Inspiring
March 8, 2019
I think if you had implemented it properly at the get go, it would have been better received. It's mainly the inconsistency that made it impossible to work with, at least for me. Particularly in Photoshop. As for someone like myself, I use shapes, text and bitmap layers and all kind of layers all the time, often on one same PSD file and all the layers are used in different ways. I don't really regard shapes in a different way than a bitmap layers. And having to learn my muscle memory to get used to them all behaving different is impossible!. F.example: first scale a bitmap layer in uniform scale, then add a vector mask and scale, and boom it behaves differently and you make mistakes. It feels like a complete mess when working. 
If such a major behavior change for a tool that is used all the time should be changed, it should be a common behavior across the entire program (bitmaps, content aware scale, vector, text, etc etc....) and not least across all Adobe programs coming out at the same time - so you are forced to relearn it. Additionally, users should be able to revert to legacy behavior the same way you did with multiple undo's, inside the program preferences. 

Without such an implementation, this feature will never be well received. 
Inspiring
March 8, 2019
I respectfully disagree. I didn't want this, but as I've said many times, I know a lot of people who welcomed the change. Even professional users who wanted the option, not one way or another forced, but they liked the change. Simply reverting doesn't help everyone, and it's everyone we should be concerned about—if we want Adobe to also be concerned about them. Let's not start pitting one group against another—Adobe already succeeded in doing that.  '-}
Inspiring
March 8, 2019
Thanks David.  I appreciate the official response here.  Sanity is starting to return 😉
marcuss78290490
Participating Frequently
March 8, 2019
I feel like you should just revert this change to the older version in the official software until you come up with a better solution rather than: leave it up to people to configure there own files with a notepad 'fix'.
David Mohr
Participating Frequently
March 8, 2019
Adobe is paying attention.

We are aware that the changes we made to Transform/Resize in Photoshop have not been well-received by the user-community at large.  Sorry, that wasn't our intention.  We are looking into a solution that addresses the comments made here as well as the original problems we were trying to address.  We hope to have this fix released soon and we welcome those interested to join our prerelease program -- if you'd like to have some influence on how the application develops, we'd sincerely love to hear from you.

In the meanwhile, here is a workaround that will revert to the earlier behavior until we can get a new release ready for you.  This is the same set of instructions that Jeff posted earlier:

David Mohr
Participating Frequently
March 8, 2019
Adobe is paying attention.

We are aware that the changes we made to Transform/Resize inPhotoshop have not been well-received by the user-community atlarge.  Sorry, that wasn't our intention.  We are looking into asolution that addresses the comments made here as well as the original problemswe were trying to address.  We hope to have this fix released soon and wewelcome those interested to join our prerelease program -- if you'd like tohave some influence on how the application develops, we'd sincerely loveto hear from you.

In the meanwhile, here is a workaround that will revert to the earlierbehavior until we can get a new release ready for you.  This is the same thing Jeff shared earlier:


Image is not available

marcuss78290490
Participating Frequently
March 8, 2019