> EventsDisabled would suggest to me that events  have been disabled,
which is not strictly the case.

True. Just plain "Disabled" seems better to imply (or do we
infer) that *that* particular (event) Sub is disabled.


> It's a nested call, which is why I named it what I did.

No problem there. I have the other case. (also remember, I'm the
guy using lots of Globals) (;-)



> ...when you come back  to the code  at a later date, so use a variable
name that you're comfortable with.

Yep. In 6809 assembler, I developed a laser light show
choreography system in the 80's. [kids love it on Halloween] Now,
understand that I comment out-the-wazoo, for maintenance, and work
hard to make the comments descibe the purpose of an instruction, not
the instruction itself. Some years later, I was reading the code and
found one instruction -- and for the life of me, I could not figure
out its reason for being there. It appeared to be a do-nothing in
that particulat routine. - I know I wouldn't have put it in just for
timing because I was counting cycles - trying to pack as much in the
image rotation code for this 900KHz machine. Code maintenance is an
important consideration in source code.



> ...name it "xx", then do a global change  later.

I'm always using this type of out-of-the-box thing. Thanks for
the reminder.


> Off...
Yea. What is off !?