The community Taskforce initiative has now come to a close.
Thanks to everyone who made thoughtful and genuine contributions to the website.
All submissions will be kept publically available for the forseeable future for reference purposes.

This website is part of the community Taskforce initiative

Submission details

promote
29 +32/-3 votes
demote
change vote

 + Option + E to force Eject Device

Submitted by DasOMiCRON on September 6, 2008 to Usability

Once mounted if any file is open from the device unit wont eject until you close this Apps, but many times we dont know wich process is open to force quit, so better than find it...

develop an  + Shift + E keystroke to force Eject Device detecting all open files from the unit and then closing it.

(sorry for my english)

Low

Medium

Not fixed

Discussion (5 comments)

Grey_Podder wrote on September 6, 2008, 6:25pm

+1
There really needs to be a way to merge submissions. You and this user have a similar idea:
http://www.aquataskforce.com/view/45

DasOMiCRON wrote on September 11, 2008, 4:13am

Changed title from [ + Shift + E to force Eject Device] to [ + Option + E to force Eject Device].

ebaur wrote on September 13, 2008, 7:45am

Although it would be nice to have a way to detect and report on what files (or apps) are open, I'm not sure a force option is a good idea. If the user was informed about what app was blocking the eject, they could review the open docs in that app and take care of them manually. By making it automatic, you run the risk of lost or damaged data, or strange behavior from apps that were expecting the resource to be there.

There are ways to force apps to quit, etc, but I'm not sure users need a quick keystroke to do it... as it shouldn't be a common operation.

dehetepappie wrote on January 3, 2009, 3:10pm

Force open would DEFINITELY be a plus - I currently have a (damaged) DVD that I cannot eject by any other way than rebooting my Mac. It's obviously a read-only disc so no application could ever be blocking it. In the absence of a 'hard' eject button, the OS should provide it.

ebaur wrote on January 3, 2009, 5:28pm

I believe even a read only source can still be blocked because it's files may be open from elsewhere. The system isn't trying to protect you from just damaging the data on the disc, but causing issues with the running application as well.

As for the case with the damaged disk, that might have more to do with the system having problems with the disk in general, not because it's trying to prevent data related issue. Or, it may still have access against it by the system processes trying to read data about the disc.

.Chris wrote on April 20, 2009, 1:15pm

Demoted because of the dumb  in the name

You might also be interested in...