uh, no. I would not agree.
In order to get this working without errors, we HAVE to implement Recycling.
Other wise you will bring bag the big bad Mem-Leak Monster we have all been
hiding from.
----- Original Message -----
From: "D. Joannou" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 17, 2001 8:16 PM
Subject: RE: Re[7]: [Dynapi-Dev] Attention...
> > It is being handled by the DynAPI. If it wasn't then it would have
> > never worked in NS.
>
> There must be some sort of misunderstanding here.
> I am using v.2.53.
> If it did work, then should I be getting a javascript error???
>
> Line number: 77.
>
> Message: c is permanent.
>
> I don't see how this is considered as "working"!
>
> Richard Bennett said I may be missing a line from the latest CVS.
> I added the line and still the same error. Anyway the workaround
> I mentioned in previous correspondence works for me for the time being.
>
> >If you look at the specificRemove in dynlayer.js
> > you will see how it works. The visibility is hidden and it is stored
> > in a recycled array. It doesn't require any work on your part to use
> > recycled arrays.
> >
> > Robert Rainwater
>
> Let's get it working without generating errors first, and then we can talk
> about the recycling bit, wouldn't you agree?
>
> Deli Joannou.
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
