Bug 616304 - Add a 'Restore' button to the trash top bar
Add a 'Restore' button to the trash top bar
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Trash
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2010-04-20 16:09 UTC by Sense Hofstede
Modified: 2010-04-28 14:36 UTC (History)
2 users (show)

See Also:
GNOME target: ---
GNOME version: ---


Attachments

Description Sense Hofstede 2010-04-20 16:09:12 UTC
There is a button for emptying the trash in the bar on top of the folder view in Nautilus.
It would be a nice addition if there was a 'Restore' button there as well to make it easy to quickly restore the trash contents.

This bug was originally reported by Davide Lasagna on Launchpad in Ubuntu at <https://launchpad.net/bugs/553600>.
Comment 1 Cosimo Cecchi 2010-04-27 11:06:51 UTC
You can restore files by selecting some of them and choosing "Restore" from the context menu, or selecting Edit->Restore from the top menu.

I don't think restoring *all* the contents of the trash is such a common operation to introduce a new button in the top bar, so closing as WONTFIX.
Comment 2 lasagna davide 2010-04-27 19:32:59 UTC
Actually, the Restore button I proposed should work only on the SELECTED elements. You select some stuff in the trash, the Restore button pops up in the top bar (or it is made sensitive as soon as the user select some files), you click it and they are restored. Usually when you go to the trash you want either to empty it or to restore an/some item/s, so i thought that having a button for both action could be a good thing. Does the WONTFIX still applies with this last comment?

Ciao
Comment 3 Cosimo Cecchi 2010-04-28 14:36:04 UTC
Davide: sorry, I misread the original description of the request in the Ubuntu report. This made me change my mind so much I implemented straight-away your request in master :)

Changing resolution to FIXED, thanks for the report.

Note You need to log in before you can comment on or make changes to this bug.