Bug 111699 - [IDE] Support SHIFT-DELETE functionality when deleting resources
Summary: [IDE] Support SHIFT-DELETE functionality when deleting resources
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P5 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
: 269671 (view as bug list)
Depends on: 70810
Blocks:
  Show dependency tree
 
Reported: 2005-10-05 17:17 EDT by Nick Boldt CLA
Modified: 2019-09-06 16:04 EDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Boldt CLA 2005-10-05 17:17:34 EDT
Would it be possible to implement SHIFT-DELETE functionality, like in Windows or
KDE? Instead of being prompted with 'Are you sure?' and defaulting to 'Do not
delete contents', this would default to 'Also delete contents', in the same way
that DELETE defaults to trash and SHIFT-DELETE defaults to permanent deletion.

I would also enjoy being able to suppress these messages in Preferences so that
I can hit SHIFT-DELETE to blow away a resource w/o prompting, but still be
prompted for DELETEs. (This is similar function to the way Konqueror handles
deletions).
Comment 1 John Arthorne CLA 2005-10-05 17:22:34 EDT
I suspect this would be tricky to get right on various platforms.  My experience
is that Shift+Delete on Windows means don't put it in a trash folder or
recycling bin, which is slightly different from what you suggest.
Comment 2 Douglas Pollock CLA 2005-10-06 10:37:38 EDT
If you want us to emulate native shift+delete functionality (including the use 
of trash bins), then we are likely to need support from SWT (to determine 
which key is supposed to do what) and we would also need support from either 
Core/Resources or SWT to access the recycling bin. 
Comment 3 John Arthorne CLA 2005-10-06 10:56:56 EDT
Bug 70810 is for recycling bin support, so you can mark this as a dup if you
like.  The task of figuring out "which key is supposed to do what" on a given
platform seems to be typically handled by the UI bindings extension point rather
than by SWT...
Comment 4 Douglas Pollock CLA 2005-10-06 11:22:41 EDT
Sorry, I thought the keys themselves changed, but they don't seem to.  DELETE   
is send to recycle bin, and SHIFT+DELETE is delete.  However, whether you 
should be prompted can be configured in Linux.  I'm not sure whether this can 
be configured in Windows XP as well. 
 
Is the recycling bin bug still "WONTFIX"? 
 
    
Comment 5 Nick Boldt CLA 2005-10-12 14:15:24 EDT
In response to comment #1, I'm suggesting exactly what Windows (and KDE) does -
SHIFT-DELETE = delete, DELETE = trash. KDE (well, Konqueror, anyway) allows you
to define whether or not to be prompted/nagged about "are you sure you want to
delete/send to trash?")

I don't want the trash/recyclebin functionality, I just want to be able to trash
a project without having to click the radio button to "remove files". Since the
existing functionality is probably quite well known and expected, I'd add the
"Are you sure?" prompt w/ checkbox for "[x] don't prompt again" like when first
exiting the platform.

One new keymap behaviour, two new preferences, and (possibly?) one new property
string (instead of "Also delete contents" change to "Also delete contents
(SHIFT-DELETE)").
Comment 6 Douglas Pollock CLA 2005-10-13 15:27:42 EDT
Just a side note: "Shift+Delete" is currently mapped to "Cut".  
Comment 7 Paul Webster CLA 2009-03-23 11:43:37 EDT
*** Bug 269671 has been marked as a duplicate of this bug. ***
Comment 8 Susan McCourt CLA 2009-07-15 12:06:56 EDT
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Comment 9 Sylwester CLA 2010-01-12 15:30:58 EST
This is very good
Comment 10 Eclipse Webmaster CLA 2019-09-06 16:04:38 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.