09-14-2022, 04:42 AM
I was only making a suggestion. Yes it takes more work and it sucks, I don't like it neither. The "SCREEN 0" was built the way it was because it was the closest thing to a MS-DOS screen as people remembered running programs from M$QB, and that console couldn't copy-paste neither. It was built like that because it was much harder to do it with "cmd.exe" console and it was going to affect portability. Eventually a way was discovered to force QB64 text output into a console anyway without a lot of interest in being consistent between that and the SCREEN 0.
People using GW-BASIC were almost never interested in capturing all output from programs or whatever was on the screen. So M$QB only inherited that behavior. This was before there was such a thing as a "clipboard". What do you think people did during the 1980's to debug program output? Create a text file and double the "PRINT" statements, one to the screen and the other to the text file, and then examine the text file for inconsistencies. Also think about the old "FILES" statement output before there was any use of it away from finding your BASIC program to load into the interpreter LOL.
This is an obvious bug you reported, though, it shouldn't display all those extra 9's making me dizzy...
People using GW-BASIC were almost never interested in capturing all output from programs or whatever was on the screen. So M$QB only inherited that behavior. This was before there was such a thing as a "clipboard". What do you think people did during the 1980's to debug program output? Create a text file and double the "PRINT" statements, one to the screen and the other to the text file, and then examine the text file for inconsistencies. Also think about the old "FILES" statement output before there was any use of it away from finding your BASIC program to load into the interpreter LOL.
This is an obvious bug you reported, though, it shouldn't display all those extra 9's making me dizzy...