Re: Onload event call to overlib (was: Problem with flash ...)
Makes sense now.
--- In firstname.lastname@example.org, "Foteos Macrides" <fote@...> wrote:
> ----- Original Message -----
> From: docdudeus
> . . . As for the other issue with the conflict, I removed the return [token] and now both functions are fired off. For my own education why is the return not necessary for an onload event but is for onmouseover or onclick? I'm not sure I understand. Is it the internal code that requires returning a function state for the latter events which is not required for the onload event?
> One does not normally include STATUS, AUTOSTATUS or AUTOSTATUSCAP in overlib calls via onclick, so that usually works out for those "general" users who always precede the overlib call with a return token. But sometimes a user does include one of those commands in an overlib call via onclick, yielding a return value of true and causing problems.
> Therefore, the current "best use" instructions are to use the return token for overlib calls only when the call is via onmouseover, and otherwise omit it, but usually force a return value of false for calls via onclick as explained in the:
> support document.