P: Doesn't constrain proportions when resizing from side handle while holding Shift key

The only way for me to resize the height (of an existing shape from when I was using the previous version of PS) is to recreate it entirely.

It's still proportionally constraining the shape. I just want to change the height of the box. 

Hi Rebecca,

So when you just do a transform (not holding shift) it still does a free transform? If that's the case can you please go to Help > System Info and then copy and paste the contents of that window in your reply?

Thanks,
Hannah

I'm doing this and both height and width are changing. I just need one to change. Even when I turn off the lock it still does it.

I couldn't agree more, making this change would've taken ages and been hugely costly which makes the decision even more baffling. 

Many of us have built careers unraveling a small inconsistency which has ballooned into a massive problem and it's 10,000 times worse when it involves code. So why go there?

Touch apps/tools are an entirely different context, it's totally fine if they work differently, especially when it comes at the expense of making all other tools within the same context work the opposite way. That's just, well... stupid..

I'm sure the story of this decision is like the millions of other corporate decisions, we've all been there and it's sad, horrible and deflating. What a bummer.

"the change probably needed to happen in a 100 different places " ... that's a fair statement. Consistency is quality. I look at all the comments that attacked this change as though the people "outside of the change" have all the data necessary to show this was pure and simple ... sloppy work. I'm not in Adobe's meetings ... I don't have knowledge of the full myriad of challenges it takes to make any one change to Ps ... but I have attended many meetings with worldwide companies making similar process changes. And sometimes ... a lot of times ... a change that looks completely baffling, had some unique challenges and/or variables that required that change to be made in the way it was made. I've also seen companies live with a burdensome, unintuitive costly process because they simply could not find an "acceptable" solution for change.

Maybe ... just maybe ... the cost to change a default constrained proportion in every place necessary to satisfy all users at once ... would have taken a very long time and maybe this would increase the development budget significantly ... and maybe this would have injected some risk to the application stability ... requiring additional resources for regression testing ... so that a final product could be released ... in 2025? with increased subscription prices? If  you had all the same data as the people making change would you still say it was "half-baked"?

I'd like to believe that companies like Adobe have some fairly intelligent leaders who understand the value of a company's relationship with it's support base (aka customers).  And that these leaders are part of the decision making process. Maybe someday I'll run into one of them in a coffee shop. If I do ... I'll ask them to at least provide a road-map next time (even if it's a work in progress) so we can better prepare. 

Hey Donnie, a fundamental change to the way graphics software has worked for 30+ years was always going to cause friction but that's frustrating, not infuriating. 

What makes it infuriating, is that the change probably needed to happen in a 100 different places across CC but it was only made in one app, in one place. 

That's low-quality work in anyone's book and that's what gets under people's skin. Yes, Adobe will write this off as 'you can't teach old dogs new tricks' but that's an over-simplification and a convenient excuse for poor work.

The half-baked way this change was implemented is well below the quality threshold for professional software, that's why I (and many others who can't be bothered posting/voting/liking) are annoyed.

It's not good enough, period.

Rebecca so you're saying that when you hold shift and transform it doesn't free transform?

Agreed. Adobe, please stop patting yourself on the back.

Please do not mark this thread as solved when it is absolutely not solved.