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

How has this not been fixed yet? I shouldn't have to alter my system files to get functionality we have had since the beginning!

For the record, I have no problem changing 'shift to constrain' to 'shift to unconstrain' here's what's amazing...

1.
Changing it on one tool, in one app creates staggering inconsistencies. All other resizing within PS (and across CC) still uses 'shift to constrain'!!! This kind of fundamental inconsistency breaks the most basic rule in all of design - consistency.

2
This change goes against 35+ years of design software convention, so it requires a little bit of thought and care. Nothing crazy, again, very basic considerations in the design world.


Either Adobe knew and didn't care, or had no clue. Both are jaw-dropping. Again, even an intern designer knows this stuff, it gets drilled into us from the very beginning.

These basic errors beg the question, what is going on? While we all get frustrated with changes from time-to-time, we've never seen anything like this. It's so embarrassing.

If you're referring to the work around that involves saving a Photoshop user configuration file, that is not against the terms of use of Photoshop.

I have to ask, how much time does it take to press command Z and then click and drag without holding the Shift key?

Don't get me wrong, I strongly prefer the old behavior of holding Shift.

> is it really asking too much to have fundamental changes done right, and communicated properly?>

I honestly don't know. I think they may have gotten lost a bit when they tried to find out what customer expectation is. I know they went along with the way it works in Affinity, but not why. Also I heard someone say this was the way it works in Microsoft. As if most of us who use Adobe software regularly care about anything except how it works in Adobe software. But if chasing new users is the paramount mission. . . or even just listening to regular users spout off about what is more "logical" . . .

But I also know that they've made plenty of changes before that were reviled, then accepted and never mentioned again. It's always been best to use Preferences, at the least at first, so people adapt and choose, but I've also heard people complain there are too many Preferences, as well as complain that they have to use them at all. They just want the defaults. <sigh>  Me, they have made changes I'm still not happy about, but then again, they've made changes that I am still thrilled they did make.

I believe when using other software that it's on me to figure out, and remember, how basic functions work. I reckon it's the same for newcomers to Adobe. But I'm not opposed to choice, and I expect that's what they're going to go for. Sure beats having the other half as angry as the first. Plenty of people think no key to constrain a transform should have been the default anyway, even people who disagree with how this was handled.

They did respond nearly immediately with a temporary "preference" fix that from all I hear, everyone is satisfied with who want to revert. I think that's taking far more accountability for the mess they created than leaving it up to volunteers to create hacks for us while we wait for them to do something elegant (hopefully). I chose not to use it for the above-mentioned reason_there are no standards, so I want to be able to choose whether or not I get along with another app or not. And stay on my toes living in a world of modifiers built on shifting sands. And I do half remember, then swear. <G>

@Ben107584:
“This change proves Adobe doesn't understand design consistency, doesn't understand professional users, and doesn't understand communication.”

Ben, this change did not come or was requested by a professional working (getting a salary) in a field that uses Photoshop for 12 hours a day.
Adobe seems to want to expand their subscription model to anyone with a wallet by dumbing the software down to appease those without a solid self taught education and without a four year degree in Graphic/Web design. This starts from places like KelbyOne who place zero value on professionalism and a comprehensive education.

The reason this is happening is the constant cheaping out epidemic that has taken over America. Most clients don’t want to pay, most employers don’t pay living wages so to pay $52.99 a month as a freelancer is a lot of money, so Adobe is making a new market for these people instead of siding with the properly educated & professional crowd of artists. This is what’s happening to us photographers thanks to that same crowd of cheap ppl who have no respect for artists: https://www.photosbyag.net/blog/2019/...

That is the worst intellectual property abuse and extortion I have ever seen! This is what’s starting to happen, with Adobe’s help, to the graphic design industry too...ever heard of Fiverr? So, Adobe wants to be in everyone’s bank statements and to do so they need to dumb down the software since those who spent four years to get a solid education at SCAD are in minority. I don’t think there are that many subscribers in reality, or not as many as Adobe hoped, so they probably think that if they make the software less complicated more wannabes will subscribe and fill out Adobe’s wallets.

Also, “Adobe” gets all their marketing colleteral from others, so while they teach how to use the software, they don’t have knowledge of how their software is used on daily basis in say “any” advertising agency. Is there anyone here from an advertising agency that was directly consulted by Adobe before this change happened? Did anyone from Adobe showed up to explain why they even considered such a preposterous change? I don’t think so. I also don’t think they care how their software is used either. Plus, those who make these changes don’t work on making advertising materials; they make software, which is not the same thing, so those folks won’t know or care how the software is used either. So regardless of calling them out on social media or here, they don’t really care because this change doesn’t affect them directly. It sucks, but companies that get this big don’t usually care and the only way to make them pay attention is to not pay for their services. It shouldn’t be this way, but people allowed it to be, so now it is.

Agreed but it was acknowledged about as well as it was announced - sheepishly slipped through. There's been no real acknowledgement of how fundamental this change is to the way all graphics software works - why not do it right?

Changing it on one tool, in one app? The inconstancies in PS alone are jaw dropping, it raises a lot of questions about how Adobe makes decisions and it brakes trust. Our clients would destroy us for breaking something so fundamental on their websites, and yours too - right?

So why not acknowledge it's huge, reset the change, then work out how to do it properly?

We're in an on-going, subscription-based relationship with Adobe, is it really asking too much to have fundamental changes done right, and communicated properly?

> The longer this half-baked rolled out is not acknowledged, the worse it will get.>

But it has been acknowledged. They never give timeline references for anything they put to the public. But they have said they're working on it. So we may not like the amount of time working on it is taking, but we won't like a "solution" that's as half-baked and problematic as the feature.

And we ought to at least be fair and say it's been officially acknowledged as a problem they're working to solve in a way that will work for us without destroying what currently is working for some of their other customers, whoever they are.

I don't blame them for staying out of this. We're venting a lot, and all their presence will do is get more rotten eggs and tomatoes thrown at them. The Staff who come here aren't the ones who fix the problems, and they don't have any control over that other than relaying we think there's a problem. We have to assume that Adobe is really trying hard to shoot itself in the foot if we assume they aren't paying any attention to what must be the longest and most vitriolic thread in this forum's feedback.

If any are longer or angrier, I'd love to see what that was all about. <BG>

Mark pretty much summed it up.

I agree we should continue to push on reverting this insane change.
Not saying we should stop or back down. continue reaching on on Twitter, reddit, Social, etc.

I just personally sort of agree with Warren about trying to remain patient and positive — but that is my personal approach to stuff. But even I get heated and angry.

If a change doesnt come around soon I will be forced to finally update to the latest version of Photoshop. I am still using the 2018 version that behaves correctly.

My question I guess is if i update and then do the UserConfig hack will that work with all future releases? Or will I have to continue to modify my config files with each update?