[josm-dev] Another 66 relations bite the dust

[Dirk Stöcker]

On Mon, 10 May 2010, Richard Fairhurst wrote:

> FWIW I suspect it isn't a _bug_ as such, but rather that the UI is
> unclear (at least to novice users) such that it is too easy for the user
> to mistakenly delete/blank the relations. Again, deleting many (66)
> relations that you haven't intentionally touched, or entirely deleting
> large (893-member) relations, is likely to be an error in most
> circumstances: the user should be made aware of what they're doing in
> terms they are likely to understand.

Very likely. But we need a hint what the users do wrong. It's like the 
"You moved xxx nodes at once, do you really want this". But we need a hint 
where to add such a question (if it is still an issue with most recent).

JOSM has no old-state --> new-state possibility. We don't store the 
original state of the database. Thus bigger changes can be the result of 
some reworks and it may be hard to detect the valid and the invalid 
cases, as you always only see the individual steps.

In the far future we have have something like this to reduce the number 
of useless deleted objects and newly created objects (e.g. splitting a 
way and deleting a part resulting in deleting old way and creating new 
one) and to better keep history in database. But I don't expect anything 
like this very soon.

Ciao
-- 
http://www.dstoecker.eu/ (PGP key available)