There were just three differences, two one-liners, and
a little bit of load-progress voodoo in the main  load checker routine.

The one which actually fixes the symptom is this which registers the
remove loader routine.
+
 LzMediaLoader.prototype.startingLoad = function ( loadmc ){
     this.checkonce = false;
-    this.loadChecker.register( _root.LzIdle, "onidle" );
+    this.loadChecker.register( LzIdle, "onidle" );
+    this.removeLoadCheckerDel.register( this, "onloaddone" );
 }

What I don't know is why registering doesn't get successfully done
by the same line of code in the initializer. But it's the same in legals.
The code in the initializer is

        this.removeLoadCheckerDel =
            new _root.LzDelegate( this,
                                  "removeLoadChecker", this, "onloaddone" );

??






On 9/25/06, Jim Grandy <[EMAIL PROTECTED]> wrote:
> This fix is for Diamond, which is happening on trunk. We are
> supporting the upcoming Diamond release as well as working on Legals.
>
> I'd rather have a diagnosis and targeted fix, rather than a port of
> Legals code. We have limited QA resources on trunk.
>
> jim
>
> On Sep 25, 2006, at 9:50 AM, Henry Minsky wrote:
>
> > The bug does not exist in legals, so the question is who/what/when
> > fixed it?
> >
> > This sounds like a Max thing, I wonder if Max remembers.
> >
> > I am going to try copying the legals loadchecker
> > methods into trunks and see if that fixes it there.
> >
> >
> >
> > On 9/22/06, Jim Grandy <[EMAIL PROTECTED]> wrote:
> >> Hey Henry,
> >>
> >> Could you look at LPP-2732 next time you come to a stopping place?
> >> This bug is likely to be causing significant performance problems for
> >> apps that load images at runtime.
> >>
> >> Thanks!
> >>
> >> jim
> >>
> >
> >
> > --
> > Henry Minsky
> > Software Architect
> > [EMAIL PROTECTED]
>
>


-- 
Henry Minsky
Software Architect
[EMAIL PROTECTED]

_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev

Reply via email to