Menu
▾
▴
RE: [Dynapi-Dev] core api -- DynLayer Questions
|
From: Pascal B. <pb...@oi...> - 2000-12-08 07:41:04
|
maybe using the document.all (real browser document.all array) or getElementById for DOM browsers .. if it returns a null value then the element is really gone, otherwise the browser still things it's there. Pascal Bestebroer pb...@oi... http://www.oibv.com -----Oorspronkelijk bericht----- Van: dyn...@li... [mailto:dyn...@li...]Namens Scott Andrew LePera Verzonden: vrijdag 8 december 2000 8:35 Aan: dyn...@li... Onderwerp: Re: [Dynapi-Dev] core api -- DynLayer Questions The major difference between the two is that remove methods simply remove the DynLayer but do not destroy it. You can remove a DynLayer and then add it back, possibly to a new parent. When a DynLayer is removed, it returns to the "unassigned" state (meaning it has no parent and no DynDocument). The delete methods remove the DynLayer and destroy all internal references to it. When you delete a DynLayer, you cannot add it back. It's gone. You have to create a new one. That said, I wish there was some way to ensure that all references to a DynLayer object were destroyed -- as long as even one reference remains, the DynLayer will still exist, and the resources it uses will not be released. I don't think one exists; there's no way that I know of to automatically detect all references to an object and destroy them. Or is there? -- scott andrew lepera ----------------------------------- web stuff: www.scottandrew.com music stuff: www.walkingbirds.com _______________________________________________ Dynapi-Dev mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
