[josm-dev] How to ask for confirmation at layer deletion or exit?

[Holger Mappt]

If we never ask for confirmations then you would be able to quit JOSM 
while it has modified data. There can be no notice about saved changes 
at that point. The earliest time to display that notice would be the 
next JOSM start. But the data might have changed on the server in the 
meantime. In the worst case all your edits are worthless because you get 
too many conflicts. To undo the changesets that cause the conflicts is 
not an option.

I agree with you on the conceptional level, but I don't see how it can 
be implemented in a sensible way.


On 2016-01-01 at 21:37 +0100 Russ Nelson wrote:
> Never ask for confirmations. It's never the right thing to do unless
> you're very short of resources, which we never are these days.
>
> Instead, provide an undo of a layer delete. When they ask to delete a
> layer that has changes in it, simply delete it, and pop up a
> non-confirmation notice that says "This layer has changes and may be
> restored using File/Open Recent".
>
> The problem with a confirmation is that it *really* deletes the data,
> which may be the wrong thing. If you're ever at a confirmation point,
> clearly somebody might not be thinking correctly, and their answer to
> the confirmation might *also* be wrong.
>
> Undo, undo, undo! Never confirm!