> clearing up the browser memory problems (although Jordi already mentioned it
> I think)
Thank you for your effort.
> so every DynLayer has a reference to atleast an HTMLDIVElement.. that has to
> be removed by setting the variables/objects to null
>
> so:
>
> DynLayer.elm=null
>
> would remove the link between the DynLayer.elm object and the actual
> HTMLDivElement, making the DIVElement get removed from memory as well.
As far as I understand, all references to HTMLDIVElements are removed
in Dynlayer.specificRemove.
What I'm still questioning is that there's a difference in memory
handling between "delete obj" and "obj = null" and that one has to
delete or assign null to the argument of DynObject.deleteChild
at all, as it is done in line nos. 78/79 of dynapi.js.
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dynapi/dynapi/src/dynapi.js?annotate=1.39#70
Stephan
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
