Hi everybody,
I just saw a funny thing. I was playing with immediate mode, so I had the canvas renderer stopped as required. Then I had the window minimized and restored back. To my surprize, the canvas renderer was back on, so I get the below exception:
javax.media.j3d.RestrictedAccessException: Canvas3D: Cannot swap buffers when the renderer is running at javax.media.j3d.Canvas3D.swap(Canvas3D.java:2208) at jdraw3d.j3d.DirectRenderer.render(DirectRenderer.java:221) at jdraw3d.j3d.DirectRenderer.run(DirectRenderer.java:352) at java.lang.Thread.run(Thread.java:536)
That's a sort of a non-documented feature, should I call it bug ?
I'm not able to reproduce using examples/PureImmediate/PureImmediate in the distribution. Please send us your test program to investigate.
Of course that I can also trap the minimize / maximize window events, but somehow I feel that j3d should not mess with stopping / starting the renderer on your back. I know that the renderer is stopped when the window is minimized - actually everything in j3d is stopped - but for that it should use a different flag to make a distinction between an automatic stopping and a user stopping.
Kind Regards,
Florin
Thanks.
- Kelvin ---------- Java 3D Team Sun Microsystems Inc.
=========================================================================== 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".
