Obviously then the keyboard focus remains on the QB64 IDE while the user program is launched. That's weird.
Some people aren't going to like a delay of any kind when the program launches but it's probably the best solution. Might want to enable "debug" mode to put in the delay, of 1/2-second or a bit less, right when the program is launched. But this is just me babbling.
Otherwise if this holding a key is a problem (*), cannot use the QB64 IDE, but a text editor to compose programs and a terminal to launch the compiler and run the created program. I almost forgot to add that there's the dialog that could be dismissed right after pressing [F5], how to get it back? (See screenshot below.) This is a good safeguard then for when a key gets stuck or when the user discovers he/she was holding it too long.
Click the mouse for "Run program" option in the IDE might produce the other problem LOL with poorly-written programs featuring "_MOUSEINPUT".
(*) It's possible with old keyboards and/or with material caught between/under the keys, as is the case with my 10-year-old laptop. A few times [F9] press causes Linux to go crazy, and so I have to try [CTRL][ALT][function-key] presses in turn to regain control.
![[Image: f5-dialog-before-run.png]](https://i.ibb.co/zHdrJ0Y/f5-dialog-before-run.png)
Some people aren't going to like a delay of any kind when the program launches but it's probably the best solution. Might want to enable "debug" mode to put in the delay, of 1/2-second or a bit less, right when the program is launched. But this is just me babbling.
Otherwise if this holding a key is a problem (*), cannot use the QB64 IDE, but a text editor to compose programs and a terminal to launch the compiler and run the created program. I almost forgot to add that there's the dialog that could be dismissed right after pressing [F5], how to get it back? (See screenshot below.) This is a good safeguard then for when a key gets stuck or when the user discovers he/she was holding it too long.
Click the mouse for "Run program" option in the IDE might produce the other problem LOL with poorly-written programs featuring "_MOUSEINPUT".
(*) It's possible with old keyboards and/or with material caught between/under the keys, as is the case with my 10-year-old laptop. A few times [F9] press causes Linux to go crazy, and so I have to try [CTRL][ALT][function-key] presses in turn to regain control.