How to prevent the debugger stopped at breakpoint stealing the focus from the debug console if there is no stepping?

[martinakos]

When the debugger is stopped at a breakpoint you can run in debug console.
I use this feature a lot. I often write code in the editor and evaluate it in the console while stopped at a breakpoint. This is very useful when exploring mathematical solutions to a problem. This works fine most of the time.
However, I often execute code that involves visualising pointclouds and other 3D objects using open3d visualiser, which I launch from the debug console, and every time I close the open3d visualiser window the editor focus jumps to the current program counter, currently stopped at a breakpoint. Then I lose view of whatever I had in the editor at that point. This happens with matplotlib windows too.
I'd like to stop this from happening as it breaks my flow of thinking to have to move the editor again to the area I'm focus on every time I try to visualise some data.

I have tried disabling the Debug: Focus Editor On Break and Debug: Focus Window on Break options but don't stop this behaviour.

I have check for similar issues:
microsoft/vscode#162873
#21669
but none give me a solution.

I've dissabled all Breakpoints too every time I visualise data with open3d but the editor still jumps to the program counter position.

Is it possible to stop this behaviour? or could this be a new feature request?

[brettcannon]

This would be controlled by VS Code itself and not our extension, so I would open a feature request at https://github.com/microsoft/vscode .