Hello > > 1. the "simple" way: > > [...] > > The theorie said that by adding something to a empty node you would > > start a "rebuild" of that node and, in the process, getting rid of > > all old references. > > Is this documented *somewhere*?
It has been posted on this list several times, and i think i have seen in a bug-report for 1.2 .... start quote: Re: [JAVA3D] RemoveChild vs Detach From [EMAIL PROTECTED] on 2004-08-26 17:48 There is a known bug with removing sub-scenegraphs from a Group. For detailled information about a workaround please refer the J3D-mailinglist-archive but as far as I remember you have to add and remove a plain BranchGroup afterwards to let the memory be released. On Thu, 26 Aug 2004 04:57:36 -0700, Melina Alberio <[EMAIL PROTECTED]> wrote: >> I am writting an application which requires me to >> refresh the screen very often. I tried using >> removeChild, but guess the memory was not >> deallocated end quote. (i shouldn't quote so much....) > > I have not tested it, but up until now it seems to work for him. > > Yes. Still does. That is the best news i heard about the problem for a long time. cu Gilson Laurent =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
