Changes between Initial Version and Version 1 of Ticket #6914, comment 3


Ignore:
Timestamp:
2011-10-02T20:19:33+02:00 (14 years ago)
Author:
mdk

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #6914, comment 3

    initial v1  
    11Because combine ways is an implicit delete, why can't you show the same warning as on try to delete a way, which is in an incomplete area? Just do the delete check on the ways which are choosen for deleting.
     2
     3A general thing about usability in this case:
     4How dose a user should know when he could do such a operation without beeing affraid, that he can corrupt the data?
     5When I came into this problem, I saw two ways which belongs to some relations, both ways belongs to the same relations and had the tags, so I decide to combine them. But I can't see, that one of the ways is also a member of a relation which is not already loaded.
     6
     7So you mean, the user must know the internal algorithem of how and when JOSM has loaded all relations, or that the relation list may be incomplete because the relations in the list of an element are loaded via other elements.
     8
     9I'm not a newbe in using JOSM, but still I have the problem when I work in areas where nearly evey thing is a MP!