.
              WHEN DOES MY CODE EXECUTE?
              ==========================
.
The creator of TAKKY was once a commercial "vb" programmer,
 so I definitely want to go over this, I easily remember being
 initially nervous "wondering" when code was going to execute.
.
"What if a CLICK occurs in the middle of MY CODE doing
 something? I could have a file open or worse. This could be
 a mess!"
.
This really isnt a concern. TAKKY can't respond to mouse clicks
 spontaneously; the click events are not interrupts at the CPU
 level. 
.
Here's how program flow in TAKKY works, and you can SEE this by
 looking at the SHORT "main program" in your code:
1) open the project
2) paint all the forms
3) waiting for a mouse click
4) found a mouse click! execute USER CODE! go *back* to #3...
.
The point I am making? After painting the project forms, TAKKY
 has absolutely nothing to do, except look to trap mouse clicks,
 and the ONLY code executed immediately upon matching a mouse
 click, is the USER CODE procedure for that click.
.
Until your USER CODE procedure is done? No other mouse click can
 happen.
.
This situation is not limited to the programmer, TAKKY itself
 obeys this. Take for example a listbox. Once the CLICK on the
 listbox has been trapped? TAKKY immediately GOES to the USER CODE
 that is matched up to that mouse click. If you ALLOW the listbox
 to open in your code, you say: 
        ListPick "form001","listboxTOPICS"
 and once that begins, no other mouse click can happen, until
 the listbox is closed.
.
you can see this same behavior during a FormPrint as well;
mouse clicks on all other objects is suspended until the called
procedure ends.
.
YOUR code is no different. Once the CLICK is matched up to your
 USER CODE procedure, program flow immediately goes there; your
 code will *not* be interrupted by any other errant mouse click.
 In fact, no other mouse click can "get through" until you 
 end and return out of your USER CODE procedure.
.
Once your USER CODE starts? There is a 'do not disturb' sign
until your code exits and returns.
.
PROGRAMMING: so far, TAKKY is not utilizing any TIMER events.
             the user is free to do *whatever* w/TIMER(s)
             this is preBETA, I honestly can't tell you yet
             if TIMER events would cause any havoc. 
.
