[josm-dev] Handling of "invisible" objects and conflict system simplification

[Upliner]

2010/6/19 Dirk Stöcker <openstreetmap at dstoecker.de>

> Conflict handling is still a field where josm needs to be improved, so
> please contribute if you have better solutions.
>

Let's discuss how we should handle visibility conflicts. I don't think that
"visible" property of OsmPrimitives should be set by user. There's no
problem when we merging data from the server: we should just update
visibility state from the server.
But what to do if we have two local osm files where same object with same
version has different "visible" attribute and user asks to merge them?
Silently ignore the conflict and assume that "source" layer has precedence?
Or ask the user to update visibility state from the server? What should be
written in the message box?

-- 
Best regards,
Upliner