Thus perhaps a video card driver issue? My suggestion was not meant to be a button was simpler than a menu, my concern is with the fact that in your example ANY action event will generate a Canvas3D.
Other potential ideas: Switch back to a non-beta JDK. Replace the fairly obsolete Voodoo card Try the DirectX version of Java 3D (not something I'd normally encourage). - John Hans Horn wrote: > > John, > > I admit, the example is not the simplest possible that exhibits the problem. > Using a button instead of a menu would have been simpler. > However, the purpose of the example was to create a simplified mock-up test > case that exposes > the same problem as my real app (where indeed I'm doing something with the > canvas3d created!). > > To add another data point: > the problem doesn't occur on my machine at work where I'm using the same > operating environment (JDK142beta, J3D ogl 131FCS, Win2k), but different > hardware (PIII 933, nVidia Quattro2). > > H. > > =========================================================================== > 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". =========================================================================== 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".
