Bug 47 - Calling setRenderingThread with same thread causes exception
Summary: Calling setRenderingThread with same thread causes exception
Status: VERIFIED WONTFIX
Alias: None
Product: Jogl
Classification: JogAmp
Component: core (show other bugs)
Version: 1
Hardware: All windows
: P5 normal
Assignee: Sven Gothel
URL:
Depends on:
Blocks:
 
Reported: 2003-11-16 08:48 CET by Sven Gothel
Modified: 2010-03-24 07:46 CET (History)
0 users

See Also:
Type: DEFECT
SCM Refs:
Workaround: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Gothel 2010-03-24 07:46:01 CET 


---- Reported by yvg 2003-11-16 08:48:49 ----

Calling setRenderingThread(...) method several times with the same thread causes 
GLException with message "Attempt to re-set or change rendering thread" to be 
thrown.

Additional check can be made to test if new value passed to setRenderingThread
(...) is the same as set before.

This happens only on Windows.



---- Additional Comments From kbr 2004-04-30 15:51:17 ----

Resetting the rendering thread to the current thread is not supported. I don't
think supporting it is a good idea. The user should be very precise about when
he or she sets and unsets the rendering thread. The Animator class takes care of
this in most cases.




--- Bug imported by sgothel@jausoft.com 2010-03-24 07:46 EDT  ---

This bug was previously known as _bug_ 47 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=47