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.
Hi Kevin, > So I guess the question becomes, can I force the order in which the > displays load? Yes. Before you make any calls to addReference(s) for the DisplayImpl that should go second, call its disableAction() method. Also construct a DisplayListener and add it to the first DisplayImpl. When it gets a DisplayEvent.TRANSFORM_DONE, then call the enableAction() method of the second DisplayImpl. Rather than construct a DisplayListener, you could probably just call getImage(true) on the first DisplayImpl. Thanks for the output. I'll take a look when I get back to work. You might look to see if there is any linkage between setRange() calls for your two DisplayImpls, that makes it matter which finishes first (it shouldn't matter). Good luck, Bill
visad
archives: