Attachments (4)
Change History (14)
by , 6 years ago
| Attachment: | 18160.patch added |
|---|
comment:1 by , 6 years ago
| Milestone: | → 19.09 |
|---|
by , 6 years ago
| Attachment: | 18160.1.patch added |
|---|
Use streams to build the set (uses distinct to avoid duplicates)
comment:3 by , 6 years ago
Alternatively, the stream could be changed from layerManager.getLayers().stream() to layerManager.getVisibleLayersInZOrder().stream().
by , 6 years ago
| Attachment: | 18160.3.patch added |
|---|
Alternative method to 18160.2.patch for only getting visible layer changeset source comments
comment:8 by , 6 years ago
No, it's just a much better way of coding this. It will have an impact however if some plugins define a "changeset source tag" for their custom layers. I could probably make use of the feature in the cadastre-fr and opendata plugins.
comment:9 by , 6 years ago
It shouldn't have any direct impact. I actually filed the bug and patch because I wanted to report the source for a data layer for a plugin I'm working on. For that plugin, I should check and see if there is a way to tell if the layer has been uploaded since the plugin data was last used, so I can programmatically return null or the source from the plugin, to more accurately reflect the data usage.
I didn't see one in my quick grep through the source code, and if I can't find one that is being called on upload, I'll probably implement that as well.



Initial patch. Adds
getChangesetSourceTagto Layer class and overrides it inGpxLayer,ImageryLayer, andGeoImageLayer.