.
               WHERE ARE ALL THE EVENTS AT?
               ============================
.
Okay, I definitely remember the original VB had, what? about
 six thousand different "events"? Okay, I am trying to be humorous
 for the preBETA. But *seriously*, there were a LOT of events.
.
I don't have a ton of events yet. Right now, any object you can
 make is click-able.
.
I figured there was no need to clutter up and double the number
 of procedures for "right clicks"; I give the "click" procedure
 LR$. (In my head? "LEFT or RIGHT")
.
I was initially going to make form load and unload procedures.
 why? Because I remembered having them in vb.
 but, it ended up that I really don't load and unload forms,
 they are just kind of "there" in the definition file.
.
This initially bugged me, but the more I thought about it:
 --- system memory was (once) measured in "KB" and then "MB"
 --- a 4-gig memory laptop? Is considered entry-level now
.
so, at least for preBETA? everything will run in memory.
.
If you want to use 15 different forms, simply put all 15
 forms in the definition file. Set them all to .visible=0, and
 turn one (or more) on or off as you need to.
.
My (initial) line of thinking, is that:
 --- you have at least 4 GIG of memory now, not 4MB, like back
     in the day vb4 hit the marketplace.
 --- I am making my own 'input box', 'message box', etc anyway
     I would just include them in the definition file, why
     would I complicate my pre-BETA life and load and unload
     stuff.
.
PROGRAMMING:
 Back in the old days, I remember I would check 'fre(0)' and it
 was a "free memory" number that would wind down towards zero,
 you would watch for it.
 I am on linux QB64, and I don't think its implemented.
.
I honestly have no idea what's going on now without a fre(0)
 to take a peek at. I assume I will see something in another
 command, or, someone will tell me what I missed. For all I
 know? QB64 will just swap out files for large arrays and I
 shouldn't worry about it; I honestly am curious.
.
