05-14-2024, 11:53 AM
Greetings all.
100% New here.
I normally program for windows, but i miss the good old days where stuff were so much simpler.
I also realize how much I have forgotten about Qbasic and the stuff I enjoyed.
My request is not really serious, but rather curious as to certain processes that I saw in VBDOS that were carried over into windows.
It is easy to use pre-existing controls in visual designers, but how on earth did Microsoft create those basic controls for VB dos??
Like: On a dos screen in QB64 I set width to 140, 50 which looks much like the old DOS screens.
Drawing boxes with Ascii codes using commands SUBs is pretty fun, but it is just lines and text.
How would one try and create a basic FORM in Screen 0 that looks like VBDOS (the draw is easy) that you could MOVE and open another?
It has to be some image clipping of sorts and event trapping?
I am having loads of fun, but i also realize how much i have become dependent on other people's designers without understanding the core processes that runs it.
Some ideas would be much appreciated.
Regards, Pete
100% New here.
I normally program for windows, but i miss the good old days where stuff were so much simpler.
I also realize how much I have forgotten about Qbasic and the stuff I enjoyed.
My request is not really serious, but rather curious as to certain processes that I saw in VBDOS that were carried over into windows.
It is easy to use pre-existing controls in visual designers, but how on earth did Microsoft create those basic controls for VB dos??
Like: On a dos screen in QB64 I set width to 140, 50 which looks much like the old DOS screens.
Drawing boxes with Ascii codes using commands SUBs is pretty fun, but it is just lines and text.
How would one try and create a basic FORM in Screen 0 that looks like VBDOS (the draw is easy) that you could MOVE and open another?
It has to be some image clipping of sorts and event trapping?
I am having loads of fun, but i also realize how much i have become dependent on other people's designers without understanding the core processes that runs it.
Some ideas would be much appreciated.
Regards, Pete