CodePad issues in debugging mode

This issue is related to the support email received on 24/07 on the BlueJ support.

I believe that it is compound of 2 elements :

1. in debugging, the codepad should not hang - is there a way to run some configuration to prevent this despite the BlueJ architecture for the codepad?
2. if users want to execute code in the codepad at a breakpoint, it is likely they want to be able to reach the local scope of the breakpoint to interact with it (like IntelliJ) - and that is another functionality. Can it be done? Is it worth the effort?

The original support message is : I'm trying to use the Code Pad. It works fine while project execution is NOT pending, e.g., I can open a project, and enter 1+2 into the Code Pad, and get the output 3(int). However, if I set a breakpoint at the first line of main, and then enter 1+2 into the Code Pad, it seems to hang, pending completion of the project's execution. If I strike Continue, 3(int) is then displayed on completion of the project's execution. This significantly limits the utility of the Code Pad for debugging. Have I hit a limitation of BlueJ, or is my setup somehow wrong, and causing the Code Pad to hang?