10-01-2025, 05:42 PM
The problem is Windows 11 comes with two different terminals.
Windows Console is the same as always and behaves the same as always. If it's set as your active launcher, it'll run, start QB64, and then quit. You might notice that brief *flicker* as the console is there for a split second and then disappears at start up.
Windows Terminal is more of a Powershell tool, meant to replace the Console. If it's set as your active launcher, it'll run, start QB64, and then... just sit around in the background and wait for QB64 to end. If you close it, you also close QB64, which it opened as a child window.
Bert explained how to change so your system defaults to the Console and not Powershell, but the issue there is many of the console commands are being depreciated and obsoleted over time. (like the ever so useful wmic command) New commands need to be PowerShell scripts and those won't always work in the Console, so programs like some of the text-to-speech code which I've written and shared on the forums here won't be guaranteed to work for you with the Console.
So people looking for future development, rather than past compatibility swap to using the Terminal, as eventually most predict the Console will eventually be phased out completely. But the Terminal is a window that doesn't disappear auto-magically. That's what the initial post was all about.
And the only real solution that I've found?
Have it auto-hide itself to the icon tray. It's still there, still running, still accessible. But it's now hidden and out of sight, as I highlighted above.
So yeah, bert isn't seeing the problem because he's not using the Terminal. He basically walked you through the steps to stick with the older, becoming more outdated all the time, Console.
Anyone on older versions of Windows won't see this at all, as Win 11 was the introduction of this dual-option. Win 10 and lower just had the console as default. Win 12, which we always hear rumors about, will probably be *just* the Terminal, with the Console gone completely unless you download it as an extended package/external program manually.
Windows Console is the same as always and behaves the same as always. If it's set as your active launcher, it'll run, start QB64, and then quit. You might notice that brief *flicker* as the console is there for a split second and then disappears at start up.
Windows Terminal is more of a Powershell tool, meant to replace the Console. If it's set as your active launcher, it'll run, start QB64, and then... just sit around in the background and wait for QB64 to end. If you close it, you also close QB64, which it opened as a child window.
Bert explained how to change so your system defaults to the Console and not Powershell, but the issue there is many of the console commands are being depreciated and obsoleted over time. (like the ever so useful wmic command) New commands need to be PowerShell scripts and those won't always work in the Console, so programs like some of the text-to-speech code which I've written and shared on the forums here won't be guaranteed to work for you with the Console.
So people looking for future development, rather than past compatibility swap to using the Terminal, as eventually most predict the Console will eventually be phased out completely. But the Terminal is a window that doesn't disappear auto-magically. That's what the initial post was all about.
And the only real solution that I've found?
Have it auto-hide itself to the icon tray. It's still there, still running, still accessible. But it's now hidden and out of sight, as I highlighted above.
So yeah, bert isn't seeing the problem because he's not using the Terminal. He basically walked you through the steps to stick with the older, becoming more outdated all the time, Console.
Anyone on older versions of Windows won't see this at all, as Win 11 was the introduction of this dual-option. Win 10 and lower just had the console as default. Win 12, which we always hear rumors about, will probably be *just* the Terminal, with the Console gone completely unless you download it as an extended package/external program manually.
