09-04-2024, 09:34 PM
Thanks for the excellent explanation.
adding $ScreenHide does help not showing the screen when in console
when starting with double-click, first the console will be there briefly, but as I understand that is inevitable with $console applications.
The fact that with no params the console immediately returns when screen is starting is NOT an issue for me; once the user gets in the screen, he will stay there and do everything interactive (using mouse & graphics to set parameters)
So I guess (with $screenhide) I have the best possible and live with the brief flicker when starting in interactive mode...
Thanks!
adding $ScreenHide does help not showing the screen when in console
when starting with double-click, first the console will be there briefly, but as I understand that is inevitable with $console applications.
The fact that with no params the console immediately returns when screen is starting is NOT an issue for me; once the user gets in the screen, he will stay there and do everything interactive (using mouse & graphics to set parameters)
So I guess (with $screenhide) I have the best possible and live with the brief flicker when starting in interactive mode...
Thanks!
45y and 2M lines of MBASIC>BASICA>QBASIC>QBX>QB64 experience