bug when using _Dest _Console

[mnrvovrfc]

For a copy of something that is output, I recommend using the _Clipboard, otherwise there is only a screen shot.

Could build a function that prints to the SCREEN 0 as well as to the clipboard, then save clipboard contents to a text file but have to be clever enough about it. Otherwise must keep a text file open for output while displaying to the SCREEN 0, and to add to the file. It sucks and could be frustrating when the programmer forgets to do it and needs to debug the program based on its output.

It's easy to become spoiled by "PRINT" statement so that a programmer dreads having to use a "SUB" or "FUNCTION" instead for any "PRINT'ing". But it must be done in a few cases where a console-only program is not practical for the purpose.

The "$CONSOLE:ONLY" antics reminds me of Liberty BASIC 32-bit on WindowsXP which had a "mainwin" that looked like Windows Notepad, and had a similarity to QB64's non-console screenie. It was like Notepad allowing the user to write any text he/she wanted with program output and save it to a text file. Liberty BASIC had a command called "nomainwin" which wasn't recommended used except for graphics-only programs.

It still exists although it's a little bit stale:
https://www.libertybasic.com/

Telling by the "Video" unit of Free Pascal and other places it's a real itch programming for the console on Linux or Windows, so it's a doubt that something like the "mainwin" of Liberty BASIC could become an alternative to the SCREEN 0 of QB64. We might have to vote for it.