Worst Function in an Application EVER!

Question

Just using the Capture function and 50 mins into the capture decided I didn't want to run to the end of the capture process so hit the "Esc" key to stop the process.
The system then decided that what I really wanted was not to stop the import and keep what it had done, but that I REALLY wanted to dump everything!!!!!
I know there is probably a way to stop the capture process without loosing everything but WHO in their right mind wakes up in the morning and thinks "lets add a one button feature to a capture process which dumps ALL data which has already been brought in during a capture process"????????????
IMHO no matter what key is pressed what has already been captured should NEVER be dumped until the user expressly decides he wants to, and he should always have the option of restore what is lost!

Answer 1

As already expressed Robert,
When you hit escape during "Capture Now" the clip is saved ... that's because no previous clip limits were defined, starting the capture defines the in point, and stopping it defines the out.
When you hit escape during "Capture Clip" the clip is not saved ... that's because you have aborted the capture of a clip where you have already pre-defined the clip limits, and in that sense you ARE expressly deciding that you want to dump the capture.
Whilst this may be a frustration for you this time, it would be equally frustrating for others who really DO want to abort their captures, maybe because they have perhaps incorrectly defined the in In/Out point, or more likely just put the wrong tape in the deck.
Oh well, lesson well learnt I guess, and a worthwhile reminder for all of us
After all is said and done though, I'd agree with you in as much as this kind of action should be configurable. Apple have a tendency to simplify for simplifications sake. My feeling is that the preferences should go very much deeper than they presently do allowing far more custom control of application behaviour. There is so very much that could be improved within FCP that could be enabled by a deeper user preference set , whilst still maintaing its basic out of the box simplicity.