Cursor incorrectly shows previous tool selection

  • 1
  • Problem
  • Updated 10 months ago
I've updated to PS 20.0.5 (Mac OS 10.13.6) and there's a problem with the cursor reflecting the previous tool selection until the tool is actually applied to the canvas.

For example, I'm drawing with the brush, and I hit 'e' for eraser. The cursor symbol is still my brush, with the brush's size. When I poke the canvas, the brush cursor suddenly turns into an eraser cursor, and it erases.

This means that whenever I switch tools, there's a mismatch between what my cursor looks like and what it's going to do.. inconvenient.

This doesn't happen consistently, but when it's happening the problem occurs for many subsequent tool changes.
Photo of Michael Prescott

Michael Prescott

  • 18 Posts
  • 3 Reply Likes
  • inconvenienced

Posted 10 months ago

  • 1
Photo of David

David, Official Rep

  • 3567 Posts
  • 607 Reply Likes
Hi Michael,

There is a feature called Spring-loaded Tools, where if you press-and-hold a shortcut, the tool changes, but only for as long as you hold the shortcut.  This sounds like the opposite, but could that be a factor?  Also, if this is happening intermittently, that would lead me to believe there's another factor involved.  Have you turned off GPU, by chance?  What kind of graphics card are you using?  What kind of keyboard?  Virtual language?

Thanks,
David
Photo of Michael Prescott

Michael Prescott

  • 18 Posts
  • 3 Reply Likes
I didn't know about spring-loaded tools! That's cool, but I don't think that's related. As you say, this behavior is quite different. It's only happened to me twice, each time a string of problems across multiple tool changes; each time solved by restarting Photoshop.

No change to GPU settings, acceleration is still on.

I'm using an iMac from 2017 with an AMD Radio Pro 580.

Keyboard is a Microsoft Ergo Sculpt.

Virtual language: not sure what that means.

Thanks for your help!
Photo of David

David, Official Rep

  • 3564 Posts
  • 607 Reply Likes
Howdy Michael,

This only happened twice?  What were you doing when this happened?  Were you working a specific filter or functionality?  I'm asking cuz I'm both the shortcut guy and the type guy, but I haven't heard any other reports like this on the forum, despite being on here every day.  I'm wondering if this might be an isolated incident or if it's a function of using a specific workflow.  Either way, I can get fixed what I can't replicate, so any info you have is helpful.

If you had this happen twice recently, go ahead and try with GPU off.  If it doesn't happen again, then that card might have an issue.  But at the moment, I'm still trying to diagnose what's going on.

Thanks,
David

p.s. -- virtual language: if you're running a Turkish/Korean/French keyboard set to a virtual German/Spanish/English layout, etc.  Oh, what kind of mouse/pointing device do you have?
Photo of Michael Prescott

Michael Prescott

  • 18 Posts
  • 3 Reply Likes
I was using the brush and eraser tools in a large (1.6Gb) PSD that I've been working with, on-and-off for a couple of months. I was painting on a layer that has a two stroke effects applied to it.

I've never seen the behavior until I upgraded to 20.0.5, at which point I saw it immediately. 

I use a Wacom Cintiq 12WX as my pointing device, but I was changing tools using the normal keyboard commands ('b', 'e').
Photo of David

David, Official Rep

  • 3564 Posts
  • 607 Reply Likes
Thanks, Michael.  That's almost certainly the missing piece of the puzzle.

So, I don't use a Wacom tablet myself, but I read this forum every day and I constantly read about problems with this particular brand of tablet coopting shortcuts and sending the app false input -- which is the exact problem you're describing.  In my experience helping users, in these kinds of situations, 98% of the time (no exageration) if you remove the Wacom tablet the problem goes away.  There might be updated drivers on Wacom's site and I would definitely report the problem to them (I would, but since I can't repro it and I'm not a customer...), they will probably address it in their next update.

I know, not what you probably were hoping for, but I hope it helps,
David
Photo of Michael Prescott

Michael Prescott

  • 18 Posts
  • 3 Reply Likes
Maybe. This seems a surprising conclusion, since the mismatch was between the tool cursor shown on screen and the actual state of the application.

The Wacom doesn't control what's drawn on screen (i.e. what's in video memory) as far as I know, it's just a monitor/mouse/keyboard. For the Wacom to be a problem, it would have to:

1. Intercept me pressing 'b' on my keyboard, and not convey this information to Photoshop.
2. Remember what tool I had selected
3. As I draw, send not only the mouse-drag event stream but the batched-up tool change command, which it always got correct.

Doesn't a race condition in Photoshop's use of the OS-level cursor API seem like a simpler explanation?

Anyways, since it's not reproducible (I can't make it happen any more) perhaps we'll never know!
Photo of David

David, Official Rep

  • 3564 Posts
  • 607 Reply Likes
The best test would have been to work without the tablet.  At least 9 times out of 10, problems like this disappear immediately.  Please try this if the bug returns.

Thanks,
David