| 9 | | are meant to show a dialog asking the user for a response when there are conflicts. The difference is that the `if` part implements what I described with "adds code to check if a conflict exists where one or more tagged ways don't have the same tag value and - if so - show the conflict dialog." |
| 10 | | (I should have written OSM objects instead of ways.) |
| | 9 | are meant to show a dialog asking the user for a response when there are conflicts. The difference is that the `if` part implements what I described with "adds code to check if a conflict exists where one or more tagged ways don't have the same tag value and - if so - show the conflict dialog." in the svn commit. (I should have written OSM objects instead of ways.) |
| | 10 | |
| | 11 | I wouldn't want to have a different behaviour in action `Replace Geometry` and `Combine Ways`, they should just depend on the user preference. So I see no reason to change the code in utilsplugin2 (besides the refactoring changes). |
| | 12 | |
| | 13 | My understanding of the problem with the conflation plugin is that users may want to ignore the setting `combine-conflict-precise=true` when using this plugin. Always or just in special cases where many objects are treated? |
