Program Error trying to nudge or move paths with the pen tool selected - open or white arrow ok.

  • 1
  • Problem
  • Updated 9 months ago
When editing a shape in Photoshop with the pen tool, and holding control (Windows 10) to select points the object can not be moved or nudged without a program error. 





This behaviour does not present when using the white arrow.
Photo of matarua

matarua

  • 2 Posts
  • 0 Reply Likes

Posted 10 months ago

  • 1
Photo of Eric Floch

Eric Floch

  • 1 Post
  • 1 Reply Like
Hi! I've been taking a look at this in our shipping version of Photoshop CC (19.0.1), and I'm not seeing the program error you're experiencing when I try to move or nudge a path created by editing a shape. So, I have a few questions for you...

-- Have you been able to resolve the problem in the past few days? If so, what fixed the issue?
-- If not, let's try to dig into this... What kind of shape are you trying to edit? Rectangle? Ellipse? Custom shape? If custom, what kind of shape?
-- If it's something heavily edited or non-standard, it would really help if you could get us your test file. Is this something you'd be willing to do?
-- When you're trying to nudge or move, do you have the standard Pen tool selected, or the new Curvature Pen tool?
-- How many points on the path do you have selected when you're trying to nudge or move?

Basically, any help clarifying what you're seeing would be extremely helpful, as I'm not seeing the issue with any standard cases.

Thanks so much!

-Eric Floch
Photoshop Quality Engineering
Photo of Colin Wiseman

Colin Wiseman

  • 2 Posts
  • 0 Reply Likes
Adobe Photoshop CC 2018
Just installed/updated less than 1 hour ago.
I get this error as well when trying to nudge an item. It was working fine, but it stopped working.
Closing and reopening Photoshop fixed the issue.
Bit rubbish really!
Photo of matarua

matarua

  • 2 Posts
  • 0 Reply Likes
Seems resolved for me now, currently on version 19.0
Photo of Colin Wiseman

Colin Wiseman

  • 2 Posts
  • 0 Reply Likes
It resolved for me when I restarted, but it wasn't the first time it happened. It won't be the last.