On 6/17/2001, 1:01:50 AM EST, D. wrote about "[Dynapi-Dev] Attention...":
> What do you mean Robert?? Is THAT good news?? LOL
> Obviously it is not handled by the DynAPI, because
> the deleteChild function instead of hiding the layer
> does a "delete c" as we know already.
> If what you say were true, then THAT shouldn't be happening.
> simple!
> Correct me if I am wrong, but people should then bare in mind that
> it's not being handled for Netscape at this very moment, although
> it was intended to have been, and will be probably some time in the
> future. For the time being, I guess, people should be doing a
> removeChild() and a setVisible(false).
It is being handled by the DynAPI. If it wasn't then it would have
never worked in NS. 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.
> I was not aware of the built-in recycling and haven't got the faintest
> as to how to use it, although I am sure that it would be very usefull.
> Deli Joannou
--
Robert Rainwater
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
