Mouse moves trigger costly calculations to early

[GerdP]

Each mouse movement across the rendered data triggers a lot of costly calculations, this is done to highlite the object(s) under the cursor. I think this should only be done when the mouse stays at the same location for a while. Is there any option to configure this?

[skyper]

Replying to Gerd Petermann <gpetermann_muenchen@…>:

Is there any option to configure this?

See Display -> OSMData in preferences

[GerdP]

Don't understand. I don't see an option to set a time. WHaat option will help me?

[skyper]

Replying to Gerd Petermann <gpetermann_muenchen@…>:

Don't understand. I don't see an option to set a time. WHaat option will help me?

Sorry, only available option is to disable the highlighting completely.

[GerdP]

The attached (experimental) small patch avoids a redraw in two situations when in Select Mode
1) Mouse is outside of the MapView and one of the special keys is pressed
(This is done by setting oldEvent = null in mouseExited(). Without this change highlighted elements change when you press e.g. Ctrl)
2) Mouse is moved quickly, there is no need to highlight something in this situation as the result is unpredictable.
I've added a log message to show how often this avoids the costly call of giveUserFeedback() and possibly the repaint.

I see no negative impact on user feedback, so this should just save a lot of CPU cycles which might help on battery driven machines.

The hard coded numbers work fine for me, I assume they should depend on e.g. screen resolution, something like "distance between mouse
events" > x % of screen resolution.