>Did you issue a NODEFAULT after the DODEFAULT() ?
>
>If you did not, the net effect would be a "double click".
Ah...very interesting....but still a very strange way for inherited class behavior to function.
It is not clear at all from the documentation that issuing a dodefault() (without first issuing a nodefault) causes the baseclass to do double duty. This seems to be a direct result of the fact that some event methods always execute some behavior related to the baseclass (unless you use NODEFAULT) even when the corresponding method of the subclass contains code.
I find the official documentation of this aberrant behavior to be sorely lacking.
"The Iron Fish: The water is cold...but the fish don't mind"
...Jay Jenks, boyhood chum
