Changeset 1078 breaks "Draw boundaries of downloaded data"

[avarab@…]

See attached screenshots, the hatching of non-downloaded areas doesn't work if opening an .osm file from the filesystem or if multiple areas are downloaded through the API.

Even if this worked as it was intended to do I think it should still be reverted, it makes editing data (e.g. from landsata data) outside the downloaded area distracting. Sometimes you know there's nothing there and JOSM will already give a warning when you upload telling you that you edited outside the downloaded area.

[avarab@…]

Displaying an .osm file from the filesystem

[avarab@…]

Multiple layers from the API

[avarab@…]

Multiple layers from the API 2

[avarab@…]

Multiple layers from the API 3

[anonymous]

The hatched area behaviour has been significantly changed in r1082, please check if that works better for you. The download bounds should be saved with any .osm file you save from JOSM so that re-opening it in JOSM should display the correct "downloaded area". However, loading files from other sources or old .osm files might really be a problem. I will investigate this and remove the hatching for situations where no server contact has been made.

[framm]

Hatch pattern now drawn only where bounds are defined, i.e. either if the .osm file you load has a <bounds> object or if you get data from the server. Also, no hatch pattern for inactive layers. Applies from r1083.