I'm using transform box controls a lot, especially click the edge, then right click to choose warp/perspective etc...
And after the latest update, whenever i click the edge of the transform controls, it lockes, and rasterize the image as i move the mouse.
I'm not holding the mouse when i click, so that's not the issue.
Looks like it went back to the old way - hold down shift.
Thank you for your answer, but that is still not the solution. The problem still exists. But i see what is your point.
Actually i'm not trying to rasterize the photo proportionaly or vice versa.
My point was, that when i click and release the edge of the transform control lines that are visible around selected layer, it behaves like i'm still holding the mouse left click, so it drags the edges and it rasterizes the image.
That started happening after the latest updates.
- Before, i just left clicked the transform control line, to enter the free transform tool, so i can go right click and pick something like warp, perspective, distort etc...
I still have no idea why this problem occurs even after i tried reinstalling ps. It's quite annoying.
I understand now - that is very frustrating. I'm sure it has something to do with the graphics card - mine is no longer compatable and wreaking havoc.
Having the same exact issue. I hope this gets resolved fast, because it's not only annoying but making my efforts greater.
Same thing here, I think this option was changed in the last update.
And I'm trying to figure out how to disable it.
I also have this problem and it is very frustrating
Thanks! When you reset the move tool it actually works!
Did you restart Photoshop to work?
Because here it's still the same, when I just click on the square of the object's tranform and release the click it sticks and only when I click a second time can I stop changing the object's size.
Nope, i just picked the move tool, and restarted it like Andrew said, and now it's working perfectly. 😕
Actually the problem still occurs... Yesterday, after resetting the move tool, today that error is back. 😞
same here and it is frustrating