NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Bill- Bill Hibbard wrote:
This would be a nice way to re-use an IDV, if all the memoryleaks in the IDV, VisAD and Java3D can be plugged.
Oh, yeah, that was the issue with re-using a display that I forgot to mention - memory leaks. As you say, it would be important to plug those first. Thanks for the other suggestions. If the
IDV always re-used one DisplayImpl, that would help.
I'm not sure what you mean here, but the IDV main window always has the same DisplayImpl. It gets constantly rebuilt when DisplayControls are added/removed. You can create new DisplayImpls in separate windows, but the main one uses the same one over and over and over again. Don ************************************************************* Don Murray UCAR Unidata Program dmurray@xxxxxxxxxxxxxxxx P.O. Box 3000 (303) 497-8628 Boulder, CO 80307 http://www.unidata.ucar.edu/staff/donm *************************************************************
visad
archives: