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

"btw what do you mean by 'A true "but ours goes to 11" moment...' ?"

Reference to a gag in the movie This Is Spinal Tap.

One of the musicians points out how most amplifiers go to 10, but theirs goes to 11. When interviewer points out that that just means their "10" is louder, the musician says "but ours goes to 11".

Yes, it is how that works. I'm coder too so I do my job, but when that is done I test it so long I know that's perfect. Of course that's me, single person, not a company that have people for every task in the long process. But when I have occasion I engage people who do that for me, who are freaks or everyday users that will do use that was made, and used so far in the previous form if that wasn't avialable yet in other version. Big Adobe could learn much from small, weak companies, but powerful by their profesionalism, as in their case that is be or not to be in the bussines.

Those seconds are ironicaly people who come with ideas, but it doesn't seem try them in practise. Regarding first issue testing the product happnes for sure, but if that was also used by people who made this stuff we had not so much inconsistency refered to only one feature. If you agree to be a beta tester in alpha phase then okey, pay for it, but I wouldn't expect everyone is going to follow you. When I screw up that I done for others, a man that pays for it, is only me, not my customer.

Adobe does it other way, with their own caveat for situations they are guilty but accordingly to regulations not responsible for that they did wrong.

Defending or explaining them saying of marketing and all other sections means for me only that they are not able to do it right way. I agree everyone makes mistakes, but it happens to them too often, while million users has to deal with. Someone on their side should think to be replaced immediately, or that's simply their way for unrespectful bussines.

After further testing this little operation also seems to have fixed that absolutely stupid and idiotic behavior of committing your transform simply by dragging a guide in mid process. This is huge. It fixes almost everything that was wrong. Of course, I've just scratched the surface so who knows what will pop up. 

I wouldn't say that is hard to make that checkbox in Options Bar (while they did much harder stuff!), so I feel like we don't have to do with big company but someone pretending to be seen so.

Loll I was giving other examples like enforcing left handed to act like right handed after whole life beeing that first or running forward from now on while you're turned back to your usual direction.

btw what do you mean by 'A true "but ours goes to 11" moment...' ?

"IMO, it would have worked out a bit better if all the Adobe apps adopted the change at the same time, and if there weren't so many inconsistencies, and they even still gave us an opt out box to check — but my opinion is worth what they pay me for it."

It'd work out a bit better if someone at Adobe who actually used the program often enough and deep enough or consulted with those who do really thought about WHY they are about to make a sea change in the way certain tools work. So far  I have yet to see a single explanation that passes the smell test - y'know - one that's not from someone linked to Adobe that tells us WHY someone thought this was really a good idea, where it came from and who approved it. When I see Adobe employees defending the indefensible it just reminds me of the presidential press secretary doing the same. 

> but they are not graphic artists using Photoshop (Illustrator, etc) as a graphics tool>

Probably not, as most of us aren't programmers who understand what it takes to keep this creaky old tub afloat.  But are you saying that those closest to all of us, those engineers and product managers whose job it is to listen to us, haven't been paying attention to our ranting about changes release after release? I can accept that they might not be able to judge accurately the disruption one change will bring versus another, but they do know we're likely going to complain about it.

And if 75% of their reports on "usability" say that Shift to constrain goes against all the other apps out there and disrupts  workflows with people (of whatever skill level)  trying to remember what to do, then they might think they should address it and not continue to be the outlier. Get it over with now and in another version, we'll all be used to it. Of course, I know I still remember things they took away or changed, along with what they've never done at all,  but . . .  '-}

IMO, it would have worked out a bit better if all the Adobe apps adopted the change at the same time, and if there weren't so many inconsistencies, and they even still gave us an opt out box to check — but my opinion is worth what they pay me for it.

I'll still say these engineers and product managers are pretty knowledgeable, and very likely use the software a deal more than we might think.  As long as I've been using the software, some 20 years now, I often get in a rut with the methods I use—after all, I'm trying to get something done and don't always want to take the time to find what might be a better or more efficient method. I don't want to take the time to learn and train my my wee brain and weak muscles to change direction.

And when I'm reading about a problem someone is having, I read an Adobe person giving them a solution that I knew about, but had forgotten or not bothered to fully work through, or didn't realise worked that way at all. I'm learning from them still. So they might indeed think they're doing us a favor when we don't feel it's a favor.

I knew a designer who never had the time to learn to use Curves, but she could find time to pile on Levels adjustments that got her there in the end. It was actually faster to her to be using the least efficient method than time taken to make sense of the most efficient. Most of us, if we're honest, can relate to that on some level. Do we all use Vanishing Point to its fullest potential?

MeToo

It's a stretch to say the engineers / propellerheads don't use Photoshop at all.

The problem is that they are not professional end-users. They have basic understanding of the software they are coding, enough to dabble, but they are not graphic artists using Photoshop (Illustrator, etc) as a graphics tool, so they don't understand the disruption they cause when they change interface, delete a critical feature (like Artwork Mode in Illustrator 5 back in the 90's), etc.