Lightroom Classic: Incorrect click position on Windows

  • 5
  • Problem
  • Updated 2 months ago
  • In Progress
  • (Edited)
LR 9.2.1, Windows 10, but the issue has been there for a long time.

The issue:
When under (slighly) heavy load, Lightroom basically reports wrong click position. I believe it happens for everybody on Windows, but we kind of learned to live with that.

Step by step:
It happens everytime, but often it is a split second issue where it seems to be user's mistake }but it isn't). So try to slow things down and it will be more pronounced
1) Go into grid, display lot of photos.
2) To really slow things down, in the Metadata penal select "All possible items"
3) Click on the first item.
4) LR will start to refresh the panels (so far so good)
5) In the mean time click on other photo(s).
6) LR will register the clicks, BUT IGNORES THE COORDINATES FOR NOW
7) You can move with your mouse.
8) LR will finish processing the panels and is processing the mouse events - THE COORDINATES OF THE CLICKS WILL BE WHERE THE MOUSE IS _RIGHT NOW_ (you should have stored the coordinates from the Windows event that happened before and it would be OK)

For now the only workaround is to click and wait till the click is processed.

Why it matters:
Often when selecting multiple photos and moving with a mose the wrong ones are selected.

I think it happens for other UI elements as well. I have to be carefull when evoking a Recent Sources menu, not to move the mouse before the menu is actually opened (which may take a time if a photo is being processed), because sometimes the late click registration means it will be a few pixels off and it will select "Clear Recent Sources" for me - happened at least 10 times already.

Similarly with Filters Menu on the right...
Photo of Vít Kovalčík

Vít Kovalčík

  • 26 Posts
  • 6 Reply Likes

Posted 2 months ago

  • 5
Photo of Jerry Syder

Jerry Syder

  • 499 Posts
  • 227 Reply Likes
You are right. This must happen to all Windows users but we've just learnt to ignore the phenomenon. At first, I did think it was user error but it didn't take long to realise that there was a glitch in the Matrix and after many years, I still ignore it although it aggravates me each time. Your recipe does trigger it but so does anything that puts LR to work (creating merges etc.)
Photo of Hans van den Berg

Hans van den Berg

  • 14 Posts
  • 0 Reply Likes
I am not sure that I have noticed this. But maybe, it has to do what I experience - although I don't think so really - when working with the mouse. It happens quite often that I click and, at the same instant, move the mouse. When the mouse button is lifted, let go, the mouse is at another point than required. I have this mainly with R = crop and straighten.
Photo of Just Shot Me

Just Shot Me

  • 533 Posts
  • 144 Reply Likes
How about shutting other programs (Services and Processes) down when working in LR Classic.
Stop putting the system under such heavy load, needlessly.
Set the system to Max power to stop the throttling of all components.
Photo of Jerry Syder

Jerry Syder

  • 499 Posts
  • 227 Reply Likes
There's a bug and he's reported it as he should. And just to humour you, this happens with just LR Classic running. 
Photo of Vít Kovalčík

Vít Kovalčík

  • 26 Posts
  • 6 Reply Likes
My computer is pretty powerful and doing virtually nothing expect for working in LR. You don't need to slow it down like crazy - this was just an example. Even miniscule slowdown (by LR itself) is enough to click a few pixels from the target and this can be crucial. This is definitely bug in LR, doesn't happen in any other software. There is nothing you can do about it.

(BTW I  consider myself a power user and I am a programmer, Win32 API included - it should be enough for LR to just respond to WM_LBUTTONDOWN etc. events in such a way that you remember the coordinates that are served to you as a parameters in these events. This is obviously not happening.)
(Edited)
Photo of Jerry Syder

Jerry Syder

  • 499 Posts
  • 227 Reply Likes
Don't need to defend your post bro(shouldn't have to) - it's a bug and has nothing to do with your system's resources.
Photo of Jan Hříbal

Jan Hříbal

  • 16 Posts
  • 3 Reply Likes
@Just Shot Me this is such useless and stupid pseudo-troubleshooting comment I don't even know where to start.
Maybe don't post at all if you don't understand what are you talking about.
Photo of Just Shot Me

Just Shot Me

  • 533 Posts
  • 144 Reply Likes
You can start by not posting something like you did. And the same thing for you.
I can't count high enough the number of people that I have run into that have 80-100-150 things running on their computers and wonder why it is so S L O W.
But thanks for thinking of me. It is appreciated.