A modern programming language that makes developers happier.

kotlinlang

runconfig.png

Hi, since Quail 1 (and same in Quail 2 preview) my preferred debug layout using run configuration (logcat comes to focus, debug view pinned in the same bottom panel is not the focused window) is being overridden.
I don't often use the debug view as I do image processing, and only want it to focus when a breakpoint is hit. I've tried other workarounds which (from memory, the old way was to create a window layout called "Debug") but no avail. The obvious workaround is to pin the debug tool in a side window, but really I still don't want this behaviour when running a debug configuration - for non android run configurations in multiplatform its not as relevant as the log output. Any ideas on how to keep both logcat and debugview in the same pinned (bottom layout) in Quail? Previous versions focused logcat per my run configurations.

I'm not exactly sure what this workflow looks like. A screencast would help a lot from before Quail 1. It’s possible this is an IntelliJ Platform change, as we haven't made changes to run configurations to my knowledge on the Google side. 