| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
robust, doc Java2D/AWT properties.
On X11 disableBackgroundErase() must happen before native peer creation,
this patch issues it before and after super.addNotify().
Make drawable creation more robust, ie only create a drawable in case the size is > 0x0
and do this check/create at display/paint in case size it not yet determined.
Add documentation about Java2D/AWT properties impact on GLCanvas.
Make JUnit tests on AWT/GLProfile's more robust, while adding frame validate()
ensuring 1st paint will have a size, hence will create the drawable.
This is necessary for eg. AMD GPU's and GL context > 3.
|
| |
|
| |
|
| |
|
|
|
|
| |
exceptions
|
| |
|
|
|
|
| |
SUCCESS
|
| |
|
|
|
|
|
|
| |
an <init> exception.
Also adding current thread name.
|
| |
|
| |
|
|
|
|
| |
(boolean)success instead.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
96af6c9bf2d683115996 moved the creation of the AWTGraphicsConfiguration,
GLDrawable and GLContext to the GLCanvas constructor.
This disabled recreation, removeNotify()/addNotify() after 1st addNotify(),
since the drawable/context were already set to null.
Smart recreation, ie not destroying the resources completly:
1 - drawable
2 - context
3 - AWTGraphicsConfiguration's Device (X11: Display)
is not possible, since removeNotify() is the only destroy notification
we have from AWT, which would leave the above resources open -> leak.
This is especially true for (3), since the device is created 'on the fly'.
In NEWT we use lazy creation/destroy and are able to keep the references alive.
A remodelling of AbstractGraphicsConfiguration would be required,
which indeed would be overkill.
Simple solution is to move the creation block back to addNotify()
but before 'super.addNotify()', since it needs our chosen AWTGraphicsConfiguration.
Also flagging sendReshape in addNotify().
Added test case com.jogamp.test.junit.jogl.awt.TestAWT03GLCanvasRecreate01.
|
| |
|
| |
|
|
|
|
| |
pause()/resume() so it becomes a non critical to multithreading, hence display() or state change needs to be synced
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
simple GLSLShader test.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
429, 428 and 405
Fixes bugs WGL pixelformat related bugs:
http://jogamp.org/bugzilla/show_bug.cgi?id=397
http://jogamp.org/bugzilla/show_bug.cgi?id=410
http://jogamp.org/bugzilla/show_bug.cgi?id=429
http://jogamp.org/bugzilla/show_bug.cgi?id=428
http://jogamp.org/bugzilla/show_bug.cgi?id=405
Tested on Window7-x86 (amd/nvidia), WinXP-x32-VirtualBox.
Solution:
Cleaned up X11/GLX code to use it as a correct boilerplate
for the new WGL selection, which now duplicates the same behavior.
X11/GLX and WGL follow the common logic:
- 1st try:
- get GLCapabilities based on users GLCapabilities
- setting recommendedIndex as preferred choice
- 2nd try:
- get all GLCapabilities available
- no preferred recommendedIndex available
If no recommendedIndex has been selected and no chooser has been passed,
we use the DefaultGLCapabilitiesChooser.
Choose the GLCapabilities if a chooser is given (or see above).
|
| |
|
| |
|
|
|
|
| |
class HINSTANCE is acquired at static initialization
|
|
|
|
| |
NativeWindow+JOGL/Windows: Complete Opaque types
|
| |
|
|
|
|
| |
cause a SIGSEGV at JVM exit.
|
|
|
|
| |
to simplify usage.
|
|
|
|
| |
SIGSEGV on AMD
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Consider use cases with many drawables and no drawables at start,
this had to be reflected all over this patch set, implementation,
usage and test cases.
- GLAnimatorControl
- refine API doc / states
- add 'void remove(GLAutoDrawable drawable);'
- Animator*:
- using RecursiveLock 'stateSync' for all actions out of the big synchronized (animator) block:
- get status methods (thread, isPaused, ..), hence no more synchronized
- display drawables change, utilizing synced ArrayList swap
This removes the need for volatiles usage shouldPause/shouldStop within the display method.
- added blocking wait for state change for add(GLAutoDrawable)/remove(GLAutoDrawable) method
- remove flawed double checked locking in anim thread (pause/idle condition)
- thread is now a daemon thread, hence it won't hinder the JVM from shutdown
-
- Animator use change:
- Always resume after pause, except in case of final destroy -> NEWT invalidate / GLCanvas,
this considers use cases with many drawables and no drawables at start.
- GLDrawableHelper: Don't pause at implicit dispose()
|
| |
|
|
|
|
| |
resource at recreation or it's possible other drawables
|
|
|
|
| |
AnimatorControl to pause rendering.
|
|
|
|
| |
992dcea3e94eead998942127a137cccd0882fe97)
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
for Canvas. ; Adding FSAA test.
Canvas/X11:
The Canvas GraphicsConfiguraton should be chosen before the native peer is being created.
Choosing AWT GraphicsConfiguration (all platforms):
Don't filter our capabilities with 'AWTGraphicsConfiguration.setupCapabilitiesRGBABits(capsChosen, gc)',
not necessary (see above) and it would remove ourrequired alpha channel.
Canvas display():
Don't render if drawable is not realized (yet).
|
| | |
|
| | |
|
|/
|
|
| |
made references created in double checked locks volatile.
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
and getChosenCapabilities() return immutable instances. Add cloneCapabilities() to create a mutable clone of an immutable set of capabilities.
|
| |
| |
| |
| |
| |
| | |
eliminates the cloning that was occuring for each swap buffer call.
This is the first step in implementing immutable Capabilities.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
NEWTEventConsumer and AWTTreeLock
The unit test for NEWTEventConsumer and AWTTreeLock,
tests previous commit 'JAWTWindow: Avoid AWTTreeLock' b0b1e3fb9c0f915cdf8d237c0f61a9d08ca83b01
|