tamilyn / xee

Automatically exported from code.google.com/p/xee
0 stars 0 forks source link

Unable to delete without confirmation #216

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I'm experiencing problems using the "Delete File" (without confirmation)
keyboard shortcut in Xee. I can't get it to delete files without
confirmation using a new shortcut key or with the Delete key itself.

What steps will reproduce the problem?
1. In Xee Keyboard Shortcuts, assign a new keyboard shortcut, such as
command-t, to the "Delete File" action (not "Delete After Confirmation")
2. Return to an image window and trigger the new keyboard combination 

What is the expected output? What do you see instead?
The Delete File confirmation dialog appears, instead of the file being
deleted without confirmation.

What version of the product are you using? On what operating system?
Xee 2.1.1
Mac OS X 10.5.8

Please provide any additional information below.

With the delete key is assigned as the shortcut, it is almost as if the key
isn't being recognized at all. 

1. Remove the delete key from any existing keyboard shortcuts
2. Assign the delete key to the "Delete File" (without confirmation) shortcut
3. Return to an image window and press the Delete key 

The system beep sounds as if the key was not recognized. 

4. Move (drag/drop, or recreate) the Delete key from the "Delete File"
action to the "Delete After Confirmation" action.
5. Return to an image window, and press the Delete key.

The Delete Confirmation dialog appears as expected.

Thus:
 - Assigning a new shortcut to the "Delete File" action performs
delete-after-confirmation 
 - The "Delete" key functions when assigned to "Delete After Confirmation",
but not when assigned to "Delete File"

Original issue reported on code.google.com by matthew....@gmail.com on 31 Jan 2010 at 4:01

GoogleCodeExporter commented 9 years ago
Issue 230 has been merged into this issue.

Original comment by paracel...@gmail.com on 17 Jun 2010 at 5:16

GoogleCodeExporter commented 9 years ago
Well, I finally got around to sorting this out, and it seems to be caused by 
several different bugs, most of them in AppKit. I ended up having to completely 
circumvent OS X's default key handling to fix it. Hopefully I didn't add too 
many new bugs in the process.

Anyway, I THINK it works as expected now.

Original comment by paracel...@gmail.com on 11 Apr 2011 at 8:57

GoogleCodeExporter commented 9 years ago
Thanks! Now what should we do? Download new version?

Original comment by soulsmit...@gmail.com on 11 Apr 2011 at 11:54

GoogleCodeExporter commented 9 years ago
Once it's done, yes. Should be fairly soon.

Original comment by paracel...@gmail.com on 12 Apr 2011 at 12:14

GoogleCodeExporter commented 9 years ago
This issue somehow persists in 2.2

Original comment by expert.d...@gmail.com on 24 Oct 2011 at 5:52

GoogleCodeExporter commented 9 years ago
I need more specific information on what happens.

Original comment by paracel...@gmail.com on 24 Oct 2011 at 6:43

GoogleCodeExporter commented 9 years ago
Sorry I did not realize this at the time of writing, this problem happened only 
on files on a mount, specifically on a TrueCrypt mount. It works great on the 
Mac OS X file system though. 

Original comment by expert.d...@gmail.com on 28 Oct 2011 at 5:51

GoogleCodeExporter commented 9 years ago
That is by design. It will always ask before deleting files which can not be 
moved to the trash.

Original comment by paracel...@gmail.com on 28 Oct 2011 at 12:48