warning when deleting an object with remaining conflict

[skyper]

This is not a bug itself but the way JOSM works right now is dangerous and it is quite frustrating solving conflicts.

I have a conflict of elements with a way. This leads to have a node without connection nor tag on the active layer.

I delete this node because its "lonely" and I get no information about the pending conflict.
Yes, I should not have edited while there exists any conflicts, but this can also happen while solving conflicts on nodes with a pending conflict of elements of a way.

I am not able to restore this object (way) as it was if I have delete an element and restoring the element itself can take quit some time if you have to undo 50 conflict solutions and later manually redo them because of #4608.

version 2057

Thanks a lot skyper

[skyper]

Replying to skyper:

version 2057

sorry, version 3057

[skyper]

As deleting objects with conflict on leads to inconsistant data -> exceptions, I think we have to do something against it.

A warning might not be enough.

r3107

[skyper]

Replying to skyper:

As deleting objects with conflict on leads to inconsistant data -> exceptions, I think we have to do something against it.

I think this is one reason why it was impossible to merge two offline edited osm file with partly same objects (for example route relations but a single way might be enough).

@bastiK:
On way to get inconsistant data.

A warning might not be enough.

Still no warning.

[Hb---]

Replying to skyper:

I am not able to restore this object (way) as it was …

You could download it from the server.

[skyper]

Replying to Hb---:

Replying to skyper:

I am not able to restore this object (way) as it was …

You could download it from the server.

As far as I remember, I did merge several, offline edited, overlapping areas that time. But your are right that I could have tried to change the object in a different layer and merge it back.

[skyper]

See #18461 for missing warning with layer/file actions.