#134 LoadPanel fix for multiple calls.
I discovered that this is caused by line 55 of the
dynLayer.js. As follows:
this.elm.captureEvents(Event.LOAD); // this is nested
in an NS4 specific
area of specificCreate.
This of course dynamically (and very slyly, I might
add) captures all the
onLoad calls required to make loadPanel queue up and
just, well... work as
designed.
reference this little gem in the loadNext() function
of loadPanel (NE4
specific).
while(lyr.parentLayer) lyr=lyr.parentLayer;
lyr.onload=LoadQueue.loadHandler;
lpanel.loadElement.onload=LoadQueue.loadHandler;
lpanel.loadElement.src=url;
Now commenting line 55 out makes the Christmas tree
light up so to speak,
creating a sense of awe. Since I didn't have allot to
do with the
transition to "specificCreate" structure I'm not at
all sure "why" that line
is there. It might perform some amazing "stealth
purpose".
One can only:
1) Comment it out. Step back from the PC as NS lights
up central square in
New York on any typical evening and see if shit hits
the inside front of
your monitor.
2) Query the superfine "mindhive" of the API's
development team as to why
that code was introduced. Brain fart? Evil maniacal
sub-plot? Real
purpose? What ever, I'm sure they will chime in and
enlighten us all with
the specifics.
Laters,
Raymond
AKA Digital Strider,
AKA Original Strider,
AKA Pascal,
AKA The "rock"...
