Option to restore object to its original state

[naoliv]

For the lazy, could we have a "Restore" option (in the File menu, together with Update data, Update selection, Update modified) to restore the selected objects back to their version in OSM?

By default I was thinking to have only the selected objects restored, but maybe it could also be split into Restore data, Restore selection and Restore modified?

It's not an undelete, but a quickier shortcut to purge the object + redownload from OSM.

JOSM:

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2015-11-05 02:34:01
Last Changed Author: Don-vip
Revision: 8993
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Relative URL: ^/trunk
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2015-11-05 03:05:19 +0100 (Thu, 05 Nov 2015)
Last Changed Rev: 8993

Identification: JOSM/1.5 (8993 pt_BR) Linux Debian GNU/Linux testing (stretch)
Memory Usage: 721 MB / 9102 MB (191 MB allocated, but free)
Java version: 1.7.0_91, Oracle Corporation, OpenJDK 64-Bit Server VM
Java package: openjdk-7-jre:amd64-7u91-2.6.2-1
VM arguments: [-Dawt.useSystemAAFontSettings=on]
Dataset consistency test: No problems found

Plugins:
- Create_grid_of_ways (31603)
- OpeningHoursEditor (31696)
- PicLayer (31694)
- RoadSigns (31694)
- SimplifyArea (31694)
- apache-commons (31718)
- buildings_tools (31694)
- conflation (0.1.8)
- contourmerge (1013)
- download_along (31603)
- editgpx (31603)
- geotools (31603)
- imagery_offset_db (31694)
- importvec (31694)
- jts (31603)
- log4j (31603)
- measurement (31694)
- merge-overlap (31655)
- opendata (31695)
- pbf (31694)
- pdfimport (31694)
- poly (31694)
- reverter (31694)
- scripting (30722)
- todo (29154)
- turnrestrictions (31694)
- undelete (31603)
- utilsplugin2 (31694)

[Don-vip]

dup of #3746?

[naoliv]

I didn't see #3746 before. But it's not exactly the same thing, I think.

I see some small different approaches/issues:

• in #3746 we can't restore multiple objects at the same time (it is using the history dialog of one object at each time)
• in #3746 it won't actually discard all the changes and redownload the object, but revert it to a selected version instead; I can imagine one situation that can cause a conflict: we modify an object and in the meantime, another person uploads a new version to OSM; if we revert to the last version, we get a conflict (while with the "Reload" option we will just discard the object and redownload it).
• it's always necessary to select the version in #3746 (more clicks, comparisons, etc), while here we should just click one time, without options.

Or I misunderstood #3746?