01-12-2023, 11:27 PM
(01-12-2023, 08:59 PM)Steffan-68 Wrote: Earlier in QBasic and Quickbasic there was one.
With larger programs, or when inserting somewhat larger sound files, the check can take a little longer
last. It would be nice to see how the progress is.
But it was an interpreter doing the work. Cannot wait even a few seconds and thinking that the IDE froze? Then launch QB64PE from the terminal. But it wouldn't include when a program is actually being compiled and linked.
Something QuickBASIC didn't do that QB64(PE) does: darken the IDE while a program is being compiled to executable. That could be unsettling because there is no way to know if this is the first time, since system restart, that MinGW was launched, or "g++" and company on Linux. So trying to display a progress could leave a 100% much longer than an user is willing to tolerate. Take it from updating the operating system, no matter which one.
If you want features that were far beyond what could be achieved in 16-bit then you will have to wait a few seconds per compilation for it. It doesn't bother me, because there was always a hold longer than it was expected in QuickBASIC. After I got ahold of QB64 around 2009 I didn't like how it held when bidding it to compile, and therefore I resumed using QuickBASIC because it was overwhelmingly for processing text files, something that today I could use Lua for.