-If there's an error (for instance, attempt to read inappropriate file for the specified file type) app is stopped/paused by the debugger; if I quit, the pop up asks if I want to cancel debugging or continue
Ok, I see.
So you test your code by pressing F9 (or choosing "run" from the run-menu? Or pressing the little green arrow in the IDE toolbar? (All 3 do the same)).
That means your code is compiled, and then it is executed.
Now if your code has an error, then the debugger "pauses" your code.
Your code is still running, just kept on hold in the debugger. (you probably see the blue dots, on the left of your code?)
Sometimes there is an error you can/want to ignore, then you can continue execution.
Other errors will just keep failing, in which case there is no point to continue.
The Debugger does not make the decision if the execution can be continued.
The debugger tells you about the error, and shows the line on which it happened.
Then it holds your code paused on this line.
If you do not want to continue, then you can press the red square "stop" button (or select "stop" from the run menu).
If you want to continue, then you can press F9 (or select "run" again).
In case of a "wrong file" this will probably keep reporting errors, and stop in the end... But if you have a "try except" to catch the error, then that will work.
(( F7/F8 allow you to execute your code line by line. // I am not sure where to find any good debugger first steps tutorial. Stepping and breakpoints are debug features that are supported by debuggers for any programming language. ))
If you did not "stop" the execution, then indeed when you try to exit the IDE, it will ask you if you want to "stop/cancel debugging".
- IF you "continue", then nothing should happen. (You keep the debugger running, therefore the IDE does not exit => the IDE should keep working)
- IF you "stop" the debugger, then the IDE should exit.
I have to check, if "stop => exit" works. It should, but your description sounds as if it does not.