Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Draging the map takes too long to redraw #1448

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments
Closed

Draging the map takes too long to redraw #1448

openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments

Comments

@openstreetmap-trac
Copy link

Reporter: Beart
[Submitted to the original trac issue database at 9.51am, Thursday, 8th January 2009]

When draging the map redrawing takes quite a time (more than 10 seconds in my case) so it is far from interactive.

This has been reported on the [http://www.mail-archive.com/merkaartor[at]openstreetmap.org/msg00694.html mailing list] and a [http://www.mail-archive.com/merkaartor[at]openstreetmap.org/msg00722.html patch] has been submitted by ukasz Jerna. This patch has not been applied in SVN yet and in the meanwhile the patch is conflicting with the current version of Interaction.cpp.

@openstreetmap-trac
Copy link
Author

Author: koying
[Added to the original trac issue at 11.50pm, Thursday, 8th January 2009]

(In [13051]) FIX : Add NVIDIA_HACK in Config.pri to (hopefully) help with Nvidia slowdowns. (fixes #1448)

@openstreetmap-trac
Copy link
Author

Author: Beart
[Added to the original trac issue at 7.33am, Friday, 9th January 2009]

Thanks for that fix. The actual change in Interaction.cpp does now use invalidate(true, true) instead of the more minimal but as effective invalidate(true, false). Is that intentional?

@openstreetmap-trac
Copy link
Author

Author: koying
[Added to the original trac issue at 9.36am, Friday, 9th January 2009]

No, I used ukasz original patch rather than the more recent one.
Remember I cannot reproduce myself.

if (true, false) is good enough, I'll use that.

@openstreetmap-trac
Copy link
Author

Author: BearT
[Added to the original trac issue at 12.37pm, Friday, 9th January 2009]

Thanks again. ukasz confirmed that the more minimal version works even better and I could not find any changes. It's at least as fast as the (true, true) version.

As I see in the timeline the patch has been applied, so this item should now truly be closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant