[OSM-dev] Implementing 'undo' in Potlatch

[Richard Fairhurst]

Tom Hughes wrote:

> The problem is that Potlatch commits changes to the database in real
> time so the two get conflated together somwehat.

Yes, and I'm not keen to change that to a "click Save to upload"  
model, because a) it complicates the UI in itself, b) you basically  
need to implement conflict resolution and I don't think that can be  
implemented in a manner simple enough for the target userbase. (Nor  
necessarily simple enough for the target programmer to implement  
without fouling up the db. :| )

Don't forget that Potlatch already has a limited "abort current  
changes" function (press ESC, does admittedly need to be more visible)  
so in most circumstances you don't need to commit misclicks to the db.

cheers
Richard