Ok... Here is something I want to show you... This may look like boring BASIC stuff you've seen 100 times, but please hold on... It is not long and I promise it the video gets more interesting towards end.
Woah!!! that's very cool! How does SymbOS handle the fact that you are switching to screen 2 in fullscreen, and then once the code runs, go back to the regular OS screen?
Woah!!! that's very cool! How does SymbOS handle the fact that you are switching to screen 2 in fullscreen, and then once the code runs, go back to the regular OS screen?
Woah!!! that's very cool! How does SymbOS handle the fact that you are switching to screen 2 in fullscreen, and then once the code runs, go back to the regular OS screen?
Very well, thank you for asking.
... from technical point of view it works so that I draw a 1000x1000 window (without content) on top of the desktop so that everything gets hidden behind it. This stops SymbOS from updating the screen, so after that I can do what ever I want. When I'm done I ask SymbOS to change screenmode back and close the window.
Say, if you somehow disable ctrl-stop in basic, and you end up with some infinite loops without ways to break operations, can you still return to symbos and close the process (the whole basic window I guess, including content)? Kind of like having Windows break up an application that by itself hangs...