02-07-2025, 01:28 AM
I honestly can't imagine any legitimate usage for it. If you're going to use over 25 rows, and you know it, then WHY wouldn't you just set the screen size or _Font yourself rather than go through that nasty automatic resize of both?
But, it is what it is now, and after ... what? 20 years of QB64 code being generated with it the way it is?? It'd just be something to break someone's bad code, if we changed it now.
It's odd how our mission statement has changed, in many ways, from a simple: "QB64, where we strive to emulate QB45 code on modern systems."
Nowadays, we've been around so long, it seems our goal is: "QB64PE -- where we strive to maintain QB64 functionality, and emulate QB45 code on modern systems."
For good or ill, Galleon made a lot of these choices for the language, and they are what they are now. Changing them would only break existing code, and that's never our goal, if we can avoid it at all.
But, it is what it is now, and after ... what? 20 years of QB64 code being generated with it the way it is?? It'd just be something to break someone's bad code, if we changed it now.
It's odd how our mission statement has changed, in many ways, from a simple: "QB64, where we strive to emulate QB45 code on modern systems."
Nowadays, we've been around so long, it seems our goal is: "QB64PE -- where we strive to maintain QB64 functionality, and emulate QB45 code on modern systems."
For good or ill, Galleon made a lot of these choices for the language, and they are what they are now. Changing them would only break existing code, and that's never our goal, if we can avoid it at all.