No Rik, it has to do with the focus, granted, but has also to do with context (for pressing return). That status should be cached.
O, no. I didn't mean that the focus is the problem at
this moment.
Lazarus just runs the compiler hidden and rerouted output to itself to determine what to display in the message window. There is no input whatsoever programmed there for the compiler.
I meant, for implementing this in Lazarus, the problem would be focus. When focus is on the code window, the enter would go there.
So my suggestion would be for the message window to recognize the <enter> and then display a dialigbox, so the focus is definitely on the dialog box.
After that, the message-window should also send the enter to the compiler progress.