Skip to main content
Participating Frequently
May 21, 2012

P: Move tool targeting imprecise

  • May 21, 2012
  • 153 replies
  • 2465 views

Move Tool annoyance in Photoshop CS6.
I use the move tool alot in my work, with high fidelity mockups for interface design. I rely on precision and predictability in my workflow. In Photoshop CS6 with the move tool set to auto-select layer, i would suspect the move tool to select the excact element im targeting at which it doesn't. it automatically selects nearby elements, which is a HUGE annoyance and disturbance. It ruins the workflow, and it's unpredicable.

Is there at least an option to remove this behaviour and just make it precise as in previous versions of photoshop?

This topic has been closed for replies.

153 replies

Inspiring
October 19, 2012
The hiding (ctrl h) tip doesn't work for me.

On a side-note - Speaking of switching between CS5 and 6, I do the same. How annoying are you finding the removal of the 'arrange documents' button in CS6?

So useful in CS5 and now only accessible from the menu dropdown in CS6.
Slows the workflow down, bigtime.
45634563545
Inspiring
October 19, 2012
To be honest I haven't tested this yet (still at work). Maybe it only works when Transform Controls is turned on??? That's one of the first things I turn off with a new Photoshop install . . .
Participating Frequently
October 19, 2012
Am I missing something... How does hiding the path or transform controls remove the issue?
45634563545
Inspiring
October 19, 2012
Thank you for re-highlighting that, FT. Good find.
Inspiring
October 19, 2012
Hey matt - did you see my work around - its not so bad...

Workaround / Tip:
If you are just moving or selecting items hit ctrl + H to hide the transform controls you instantly get accurate selection. Not ideal but better than nothing to hold you all over till the fix comes.
45634563545
Inspiring
October 19, 2012
This issue is comically frustrating for me because I use CS5 (which doesn't exhibit this selection issue) at work, but then go home and use CS6, and when I do I suddenly have to "re-adjust" to the unwanted selection buffer. Always takes me aback the first time it happens - I automatically assume I'm not clicking in the right spot or there's some non-visible pixel I'm clicking by accident.

In other words, my personal experience with this issue well illustrates the uncomfortable disparity in cursor behaviors because unlike most users that just switch from CS5 to CS6 ONCE, I switch back and forth constantly haha.
(My constant switching isn't Adobe's fault of course. And it makes dealing with other changes difficult as well, even positive ones.)
Inspiring
October 19, 2012
UPDATE:
Yeah I found out last night that this is windows only it seems... I have added the bug in a separate feed.

http://feedback.photoshop.com/photosh...
Participant
October 19, 2012
It seems to be okay to me so far. I am using a Mac Pro with OS X 10.7.5 if that is relevant information.
ulrikg2Author
Participating Frequently
October 18, 2012
Yup, it's reassuring to see the issue being aknowledged officially. Our only hope now is that the when there is some news on whatever might be going on backstage, it will be shared regardless of a long time frame, it's just nice to know what the scope is (This was a friendly plead to you Chris Cox 🙂 )

On your other note:
I just tried the flick panning out, I have the same issue.
Inspiring
October 18, 2012
Good News:
I thought I should point out that at the top of the feed it now says acknowledged
Bad News:
Now all we need do is wait a further 5 months for a resolution. ;)

Tip:
For all of you finding this a big pain in the behind like me - there is a usable workaround I found. If you just moving or selecting items hit ctrl + H to hide the transform controls you instantly get accurate selection. Not ideal but better than nothing to hold you all over.

On another note:
Does anyone else find that when you have the colour picker open the flick panning doesn't work correctly? - in that you cant flick twice until the first animation is complete... may be hardware specific as this requires gpu support.