splitting ways in route relation when relation editor is open can be improved

[dieterdreist]

Previously, you would get a conflict when clicking on OK of the relation editor, after you have been splitting a way that is inside a route relation for which you had the editor open.
Currently, it will not cause a conflict but will remove one of the parts and keep the other. In principle, this is the desired behaviour. but unfortunately JOSM often chooses the wrong part to be kept (It takes the one that keeps the id, which for me results in the longer one, as I have decided not to bother which of the parts gets the id to speed up editing). It would be feasible to keep the part that keeps the route continuous, rather than creating a hole (i.e. check which part is connected to the rest, if any, and keep this part if possible).
As a second best behaviour, it could simply keep both, i.e. add the newly created way (resulting from the split) along with the part that has the existing id.

[skyper]

Replying to dieterdreist:

Previously, you would get a conflict when clicking on OK of the relation editor, after you have been splitting a way that is inside a route relation for which you had the editor open.
Currently, it will not cause a conflict but will remove one of the parts and keep the other. In principle, this is the desired behaviour. but unfortunately JOSM often chooses the wrong part to be kept (It takes the one that keeps the id, which for me results in the longer one, as I have decided not to bother which of the parts gets the id to speed up editing). It would be feasible to keep the part that keeps the route continuous, rather than creating a hole (i.e. check which part is connected to the rest, if any, and keep this part if possible).

Note, the relation editor is independent.
Only if there are no changes in the relation editor no conflict is created and no changes of the relation are made closing the editor. (Unfortunately, the relation editor is not representing the modification unless you refresh it from the data layer.) The changes of the relation are solely result of the changes outside of the relation editor. In your case, splitting the way with membership of a route relation the new way is added to the memberlist as suggested under second, below. I was not able to reproduce the situation with only one part remaining member.

As a second best behaviour, it could simply keep both, i.e. add the newly created way (resulting from the split) along with the part that has the existing id.

[dieterdreist]

splitting a way which is part of a route, with the relation editor open, removes one of the resultant parts

[skyper]

You example shows a new relation which has not been saved for the first time, e.g. the relation is not part of the data layer, yet, and the split way action does not know about it. Please, save the relation (second button on top) in advance.

[dieterdreist]

it is the same with a saved relation, I have made another screencast so you can see it.

[GerdP]

In fact an open relation editor more or less guarantees problems when you split or combine objects which are members in the relation.
I wonder if we should simply disable those actions when a relation editor window is open.

[skyper]

Replying to dieterdreist:

it is the same with a saved relation, I have made another screencast so you can see it.

Almost, but this time the button to refresh from data layer (first button on top) is activated and both parts are members if you refresh or close the relation editor.

Replying to GerdP:

In fact an open relation editor more or less guarantees problems when you split or combine objects which are members in the relation.
I wonder if we should simply disable those actions when a relation editor window is open.

The only problem I have is forgetting either to refresh from data layer or to apply the current changes to data layer and then later get conflicts. Closing and reopening the relation editor cannot be the solution for that.

[skyper]

Duplicate of #11599?