When you hit Ctrl+Enter to test a movie or you publish it, and it is a big file that takes ages to export, YOU NEED THE CANCEL BUTTON TO RESPOND immediately.
Most of the times, it either:
- does not respond at all, or
- responds only after it completes a huge chunk of export, usually almost the entire operation. This may take SEVERAL MINUTES.
This has been so for literally YEARS, and it's unbelievable that you haven't fixed something so basic and critical.
A Cancel button must by definition be the most responsive thing in a program, otherwise it is useless.
There's no way to abort the export if the Cancel button doesn't work, except kill Flash.
This may prevent you from cancelling a long export and save your work, in case you hit Ctrl+Enter and you have forgot to save before.
For god's sake, fix it.
These are user to user forums. If you have a problem with the program design that you would like to have Adobe consider addressing you need to file a report using the link below...
Adobe - Wishlist & Bug Report
-----------------------------
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
and while I agree with your frustration, there are probably other things going on that you are not considering that need to be properly managed for cancellation to occur without throwing your machine into a tailspin.
Ned Murphy wrote:
and while I agree with your frustration, there are probably other things going on that you are not considering that need to be properly managed for cancellation to occur without throwing your machine into a tailspin.
Of course, but if taking care of those things requires that much time, there's definitely something very wrong somewhere.
I won't agree with your conclusion, but that's just one opinion versus another. If it takes that long to do something, there is every possibility it takes just as long or longer to properly undo it. The ones who might know why are probably at the other end of that link I provided. Maybe you should submit there and ask if they can share an explanation.
I've submitted the report.
When cancelling an exporting/compiling operation, IF it is done properly, there's no need to "undo" an amount of things even comparable to what has been done. If that is not so, something is wrongly designed in the wey the compilation is done. And even if it wasn't so, there's always the possibility to interrupt the exporting process, free the user interface, and in the background keep doing the "cleanup". Blocking the whole authoring environment is simply ridiculous.
Also, I strongly suspect that when you click cancel and it takes ages to respond, it isn't taking long to "undo" anything, it is just still finishing doing (part of) what it was doing until it even starts responding to the request to cancel. Of course this is just speculation, but the one thing that strongly suggests I'm right is that often enough, the click on the Cancel button is simply lost, that is, it won't "take long", it just won't cancel and end up exporting as if you never clicked.
North America
Europe, Middle East and Africa
Asia Pacific