| | 4 | |
| | 5 | > try pressing CTRL+Z to undo: this has no effect in the relation editor. |
| | 6 | |
| | 7 | That's because (unlike drag & drop) this is _actually_ not implemented in the relation editor. Feel free to submit a feature request and patches. |
| | 8 | |
| | 9 | > (Drag-n-Drop can occur jut because the click may initiate a small drag if the mouse just moves 1 pixel while clicking: selecting rows with the mouse requires absolutely not moving the mouse and this is very unreliable, |
| | 10 | |
| | 11 | This is the opposite of my experience. Drag & drop only works _after_ the corresponding members have already been selected beforehand. Clicking and dragging starting from a previously unseleted member actually starts a selection and not a drag&drop. |
| | 12 | |
| | 13 | > Editing relations with many members with JOSM is still VERY unreliable and dangerous for data. |
| | 14 | |
| | 15 | No OSM editor is completely flawless when it comes to relations but JOSM is undoubtedly the best suited for the job and most reliable and definitely does not pose a danger to OSM data like you claim. |
| | 16 | |
| | 17 | ---- |
| | 18 | |
| | 19 | Now that all of this has been said: I'm not denying that you might be facing these problems, but you need to realize that this seems to be a problem with ''your specific setup'' and you need to act accordingly if you are interested in receiving any help to get this fixed. Maybe start by actually helping to narrowing down the root cause by e.g. finding out if this is/was reproducible by anyone else (for example in other josm tickets) and looking for a common denominator. |
