#9654 closed defect (fixed)
[patch] [build fix] classes that use JMapViewer shoudn't use OsmMercator directly
Reported by: | glebius | Owned by: | team |
---|---|---|---|
Priority: | blocker | Milestone: | 14.02 |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
Hi!
Fixing #7017 requires that all classes using JMapViewer stop trusting OsmMercator as projection solver. Only tilesources, that know that they are using OsmMercator projection, should use OsmMercator. All upper layers should ask the tilesource for (x,y) ?= (lon, lat) calculations.
I already made this change in the JMapViewer itself. Unfortunately, hiding OsmMercator required its API change as well, so right now JOSM isn't buildable.
The attached patch makes JOSM to use tileSource instead of direct use of OsmMercator, and apparently fixes build as well.
Attachments (1)
Change History (4)
by , 11 years ago
Attachment: | use_tileSource_instead_of_OsmMercator.diff added |
---|
comment:1 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 11 years ago
Milestone: | → 14.02 |
---|
In 6793/josm: