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

lonnyc85144968
Participating Frequently
January 1, 2019
Yes Cristen Gillespie, I would prefer something like that iver this chat forum. A chat forum is an unacceptable place to be directed to report actual software bugs.
Inspiring
January 1, 2019
https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs

Take a look at this forum. Do you like this better for reporting bugs than reporting them here?

lonnyc85144968
Participating Frequently
January 1, 2019
Adobe is a software company... a large software company. Any other software company I have ever seen has a place to report bugs ( no matter what form is used to report) and people who both field the reports and software writers that fix the bugs. Adobe directed me to this forum to report bugs. This forum is valuable for many reasons, but is not a way to report software bugs. The fact that there is no place to report bugs and that Adobe remains silent about both acknowledging that bugs need fixed as well as how upset users are over changes made to the software is is the frustrating part. I won’t use the new version for any reason until the bugs are fixed AND legacy behavior is restored... and once again, if the changes to the tools were made to make Photoshop work on an iPad, the program on iPad is not “real Photoshop “ as advertised. Users who have been using the same tools for decades should NOT be expected to reverse tool behavior in order to work on an iPad.
Known Participant
January 1, 2019
@5935398: I agree, but the "not answering" to consumers is spread to every corporation out there because our "politicians" are all corporation owners, so every law is made to suit them and not the consumer as it should be. Don't you see that even the "popular vote" doesn't matter here in America!?
I am pretty stuck using Adobe for now, and I am not happy with the fact that weekend users have a louder voice than professionals when it comes to making critical changes to this program I've been using for the last 20 years, but I don't see how this will change without people stop paying for the subscription. Sadly most just can't do that as of yet, so Adobe continues to take advantage of us and our wallets until that happens.  
Known Participant
January 1, 2019
Alexandra... Adobe has grown (with our money) to such a large behemoth that they really don't care what we (the people who pay) think.  By ignoring all these complaints, the company is acting stupidly.  Eventually, someone (or a company) will challenge Adobe with a competitive product and only at that time will Adobe realize the error of their ways.
Known Participant
January 1, 2019
Good Morning & Happy New Year!

In regards to crashing reports, I just sent one last week too after I spent 20 minutes working on an image only to have PSCC19 crash and lose everything I had worked on. As a result, I reverted back to PSCC18. 

I, however have looked forward to PSCC19 since 2017 and that was because of the new content aware fill option. I use that daily, and on pretty much every image I edit, and that tool has worked great thus far, but since PSCC19 started crashing too on top of having the free transform ruined, I had to go back to PSCC18. 

I don't think anyone is reading crash reports. I agree that it will mean having people employed and working hard to address those, but having people employed is never a bad thing, so it would be nice to have a team working on just that. The problem with crash reports is the fixing part. I mean, we don't all use the same computer configurations and software programs, so what might have caused mine to crash may not have been the same thing as the next person. I keep my computer free of software that isn't Adobe, I don't have any games, and my only issue is space; shooting RAW eats up my drive very quickly, so I have to back up and remove photos pretty frequently, but other than that there's nothing else "software wise" that could crash Photoshop. So now, how are those working on reading crash reports going to fix these for the millions of people using Photoshop who don't have the same programs and configurations on their machines? To me, that's why even sending a crash report is useless.
Inspiring
December 31, 2018
Well now we're getting somewhere. I can follow along with this. I've read others wonder why their bug report got merged with something they don't think it belongs with. I have no clue who does that or why, but obviously, a big first step would be to be absolutely transparent about it—a statement that says why they were merging the reports, and a chance for the OP to challenge the decision.

Plenty of posters never seem to come back to check for responses, so this gives Adobe a chance not to have thousands of the same bug report out there, but the poster has a chance to return to challenge it—say 1 or 2 weeks? It might be a forum software nightmare to implement it, but it would help.

<<Most software I have used over the years provides a place to report bugs with little more than a description of what the problem is and what operating system you use.>>

As I'm sure you know, that's the bare minimum in a bug report, unless the description is fairly thorough. Most bugs don't affect everyone, so unless there's enough description that steps can be replicated, a brief description isn't going to get much traction without some further interaction between Adobe staff and the poster. Which is what happens here, or at least Adobe personnel try to get to the bugs, even ones without much of a description, and also without including the OS or software version.

More personnel from Adobe, hired for the purpose, would be great. I think we can probably go whistle for it, as that's a solution even management takes into consideration, so we can assume they've already done that and decided that's what they offer through customer service.  People they hire may not be all that qualified to help, but what you asked help for does get logged—it's a bug report, if nothing else, though I don't know who looks at these from each of the apps.  But if customer service gets 1000 calls a day because customers can't get the crop tool to work, Adobe will know about it. And customer service reps are paid (something).

<<I don’t see how clicking a “ me too “ button on a subject other than the bugs I wanted to report helps with getting buggy behavior fixed. >>

??? I'm not following this. Me Too just means I've tested what the OP is talking about and it happens on my computer, too. It's not a vote in favor of getting it fixed (unlike voting for Ideas). It's a statement that you have the same, or at least extremely similar, bug. The more data they can collect on an actual bug, the more likely they are to pin it down, especially if it's one that only affects some  segment of the user base. If we all have it, they can find it quickly enough without 103 MeToos. But if only some are affected,  and they can't replicate it, if they can get people to say MeToo and accumulate comments, they might be able to figure out that it's this OS when performing this series of steps. Maybe. . .

lonnyc85144968
Participating Frequently
December 31, 2018
I don’t think bug reports need to be that complicated. Most software I have used over the years provides a place to report bugs with little more than a description of what the problem is and what operating system you use. Adobe is a big operation, and yes, should be paying someone to read bug reports in order to address problems. I came to this fourm to report bugs with the new version. Instead, my report got merged into a subject about not liking changes to the tools. I don’t see how clicking a “ me too “ button on a subject other than the bugs I wanted to report helps with getting buggy behavior fixed. The only advantage I see is that Adobe has deflected criticism from being posted on public forums that may make them look bad.
Inspiring
December 31, 2018
> I think if Adobe actually cared to hear from us about issues we are having with bugs, they would put up an actual page to report bugs rather than this dismal forum.>

How exactly would that work—differently from here, that is? A long form to fill out by each person, lots of "required" fields, then someone paid enough to be willing to read it and weed out bugs from "as designed" (meaning feature requests, actually, which the Transform/Resize redesign mostly is, even if we hate it), and weed out bugs from user error and/or unsupported hardware? For me, that would mean being paid along with the executives. I'd do it for that much.<BG>

Here we say Me Too, which both lets us see and lets them see if a lot of people have the same bug. That even works with this thread, even if it's a complaint about a working feature, and not a bug report. It also simplifies it for everyone except the original poster, since the rest of us don't have to say anything at all.   How would that work differently with an actual page for bug reports?

It wouldn't hurt, in my mind, if Adobe provided a bug report form with fields to fill out, and a place for attachments, for the willing bug reporter. It would be an awful lot of work for the person posting the bug, but it would be complete enough, we could all read the form and then decide if it's a Me Too situation or not. That might be a more "real" bug report. But would very many be willing to go to that much trouble to be the one to make the initial report, including non-English speakers, if we made that the actual page for reporting bugs?

And if we all did fill out individual long-form bug reports, how would we get feedback on our own individual bugs? We get some feedback here. Companies don't usually announce their future plans, especially if they're dependent on stockholders who definitely frown on giving away the game to the competition early. But when enough people corroborate a bug (not as-designed disliked feature which they may or may not intend to "enhance") and Adobe can replicate it, they usually do try to let us know. How would the feedback we get here, such as it is, be different with an actual bug report page and a team of bug report readers at Adobe—somehow different from the Adobe Staff we have here.

Don't get me wrong. I'm all for improving the way the forum operates—any way it makes it easier for us to post bugs that are complete enough Adobe can understand and test against them. But I don't understand what an actual page to report bugs, rather than this dismal forum, would look like, how it would be different.


Inspiring
December 31, 2018
Photoshop 2018 still works OK. If you are waiting for a reply from Adobe, don't hold you breath, you will be very blue and dead!