(01-12-2023, 01:31 AM)DSMan195276 Wrote: @kernelpanic I think I might have figured it out, it happens for me if I hold the F5 key a bit too long. If that's what's happening then I think the issue is that because I fixed the startup delay your program reaches the end basically immediately after starting. That by itself is perfectly fine, but if you're still holding the F5 key at that point then it will be picked up as input by the console and exit your program.

I would test and see if the issue still happens if you manually click the Run button, that would avoid the chance of sending any input to the console for your program. Also you could see if it still happens if you hit the F5 key as briefly as you can (though that might be hard. Maybe your computer is a bit faster then ours or something ).

Assuming that's the problem it might be worth us adding a workaround for it, we could have the IDE wait for you to release the F5 key before starting the program.

(01-12-2023, 01:31 AM)DSMan195276 Wrote: @kernelpanic I think I might have figured it out, it happens for me if I hold the F5 key a bit too long. If that's what's happening then I think the issue is that because I fixed the startup delay your program reaches the end basically immediately after starting. That by itself is perfectly fine, but if you're still holding the F5 key at that point then it will be picked up as input by the console and exit your program.

(01-12-2023, 04:13 AM)mnrvovrfc Wrote: 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? 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.

(01-12-2023, 01:31 AM)DSMan195276 Wrote: @kernelpanic I think I might have figured it out, it happens for me if I hold the F5 key a bit too long. If that's what's happening then I think the issue is that because I fixed the startup delay your program reaches the end basically immediately after starting. That by itself is perfectly fine, but if you're still holding the F5 key at that point then it will be picked up as input by the console and exit your program.

I would test and see if the issue still happens if you manually click the Run button, that would avoid the chance of sending any input to the console for your program. Also you could see if it still happens if you hit the F5 key as briefly as you can (though that might be hard. Maybe your computer is a bit faster then ours or something ).

Assuming that's the problem it might be worth us adding a workaround for it, we could have the IDE wait for you to release the F5 key before starting the program.

(I always forget it.) 

(01-12-2023, 03:03 PM)Kernelpanic Wrote:

(01-12-2023, 01:31 AM)DSMan195276 Wrote: @kernelpanic I think I might have figured it out, it happens for me if I hold the F5 key a bit too long. If that's what's happening then I think the issue is that because I fixed the startup delay your program reaches the end basically immediately after starting. That by itself is perfectly fine, but if you're still holding the F5 key at that point then it will be picked up as input by the console and exit your program.

I would test and see if the issue still happens if you manually click the Run button, that would avoid the chance of sending any input to the console for your program. Also you could see if it still happens if you hit the F5 key as briefly as you can (though that might be hard. Maybe your computer is a bit faster then ours or something ).

Assuming that's the problem it might be worth us adding a workaround for it, we could have the IDE wait for you to release the F5 key before starting the program.

Bingo! It actually has to do with the amount of time it takes to press. Where duration . . . I do not sit down on the button, I just press it briefly, like I always do.
I have tried it now: the way I always press does not work, if I consciously just "tap" it then it works. This is the case with all programs, as I have now found.

Another problem solved! But it is strange, something must have gotten faster, because today I do not press the keys any slower than I did a month ago.

• #282, #284 - The long start-up time for QB64-PE programs has been fixed, there should no longer be a delay before the QB64-PE code starts running - @mkilgore