Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Hi Scott, Thanks for the info about how you fixed your problem. > So I assume this is a better solution than fixing the problem in > VisADCanvasJ3D by trying to find which screen device the visad canvas is > about to be created on. For sure. Not really a problem in VisAD, since it provides DisplayImplJ3D constructors that allow applications to pass non-default GraphicsConfigurations. You've found a case where a non-default GraphicsConfiguration is appropriate. Cheers, Bill > PS > There were a couple of machines where the exception never happened... > maybe they had the same graphics configuration on both monitors or just > smarter graphics drivers???
visad archives: