You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: LonelyPixel [Submitted to the original trac issue database at 7.05pm, Friday, 9th January 2009]
I personally think that it's a bad idea, when more OSM data shall be
downloaded, to alter the map and the viewport at the same time. This is
what happens right now. When you're running out of loaded data and want
to load some more, that map contents change. But if that wasn't enough,
the view on the map also changes to something smaller. So at first, you
lose any orientiation and need to zoom in again to where you have just
been, to continue what you have just done.
This patch simply disables the single line of code that does that jump.
It's also a much better experience to see the map features actually
appear in the same place where none/few have been before. You get what
you want, where you want it. Ideal user feedback.
The text was updated successfully, but these errors were encountered:
Author: LonelyPixel [Added to the original trac issue at 8.40pm, Saturday, 10th January 2009]
The jumping also occurs when you go to the Preferences dialogue and press OK or Apply. It always zooms one level out then. Simply changing adjustLayers(true) to adjustLayers(false) in MainWindow::preferencesChanged() is no solution, though, as it will then zoom out really far instead. There seems to be a more general issue with setViewport() that somehow computes the wrong zoom value to set, or something.
Reporter: LonelyPixel
[Submitted to the original trac issue database at 7.05pm, Friday, 9th January 2009]
I personally think that it's a bad idea, when more OSM data shall be
downloaded, to alter the map and the viewport at the same time. This is
what happens right now. When you're running out of loaded data and want
to load some more, that map contents change. But if that wasn't enough,
the view on the map also changes to something smaller. So at first, you
lose any orientiation and need to zoom in again to where you have just
been, to continue what you have just done.
This patch simply disables the single line of code that does that jump.
It's also a much better experience to see the map features actually
appear in the same place where none/few have been before. You get what
you want, where you want it. Ideal user feedback.
The text was updated successfully, but these errors were encountered: