aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Gears/RedSquare ES1/ES2: Add proper destroy/init lifecycle incl. assertion ↵Sven Gothel2011-09-025-129/+200
| | | | | | | | | checks; Use swapInterval ; RedSquareES2 use VBO RedSquareES2 use VBO. - On Windows/NV we had to re-issue (pass down to GPU) the vertex attribute data (vertex/color), otherwise glDrawArrays crashes .. Probably a GL impl. bug. Hence we use VBO to minimize the data upload.
* Fix NEWT/Window/Windows: setSize/setPosition/reconfigure: 'nop size' -1x-1 ↵Sven Gothel2011-09-022-16/+9
| | | | | | | -> 0x0 Windows: setPosition was invoking setSize (new size propagation) even w/ nop size, let WM event wmSize invoke setSize.
* GLArrayDataWrapper: Allow vboTarget '0' -> no VBOSven Gothel2011-09-022-3/+3
|
* test scripts ..Sven Gothel2011-09-013-5/+9
|
* Test TestBug463ScaleImageMemoryAWT: Use UI Locking and AWT-EDT create/disposeSven Gothel2011-09-011-15/+34
|
* Test PIXMAP/BITMAP: Can't expect GL2/ES2 - might be SW OpenGLSven Gothel2011-09-011-3/+7
|
* Test ElektronenMultiplizierer: Unix coding of shader source (failed on ↵Sven Gothel2011-09-012-2/+2
| | | | Windows/NV)
* TestScreenMode01NEWT: Validate window size after FS toggleSven Gothel2011-09-012-3/+11
|
* NEWT/X11/Fullscreen: Fix Leaving FullScreenSven Gothel2011-09-012-11/+11
| | | | | | | | | | | | | | | NativeCode: "XChangeProperty( dpy, w, _NET_WM_STATE, XA_ATOM, 32, PropModeReplace, [ FULLSCREEN, ABOVE ] .." shall only be issued if entering FS, otherwise [ FULLSCREEN, ABOVE ] will be set on the client side at leaving FS, which is not intended. This caused a size reset to fullscreen size/mode. WindowImpl: Used WindowImpl.this.width and WindowImpl.this.height, where w and h should be used, the FS and pre-FS values.
* test scriptSven Gothel2011-09-011-5/+5
|
* NEWT/X11 Bug 502 regressions: WM_DELETE_ATOM, .. etc couldn't be catched, etc.Sven Gothel2011-09-014-99/+90
| | | | | | | | | | Use EDT X11 Display connection (DPY) for whole display/screen/window lifecycle, but the user utilization (OpenGL, ..). Only using the same DPY for creation and event dispatching allows catching WM_DELETE_ATOM 'ClientMessage's. Sync X11Window.c w/ commit 4dbb8731219212e27c9afb769a1c62b32bd230a6 - remove 'test' code .. use orig lines
* GLSL ShaderState: verbose = DEBUG ? true : falseSven Gothel2011-09-011-1/+1
|
* Test ElektronenMultiplizierer: Add original author information, split ↵Sven Gothel2011-09-014-307/+373
| | | | | | | | | | | | | | | GLEventListener/Test, .. Add original author/artist information: Dominik Ströhlein (DemoscenePassivist) Split GLEventListener/Test code Add key right/left for frame +/- 120 (fwd/bwd in time) Proper header doc formate Minor cleanup
* Test Gears: Use proper 'java' author tagSven Gothel2011-09-016-7/+7
|
* Test: Add RedSquare ES1 and ES2 standalone testsSven Gothel2011-09-012-0/+272
|
* Tests: Exchange GL2, ES1 GLEventListener to ES2 - mobile test preparation.Sven Gothel2011-09-0126-223/+86
|
* revert: a7340fd941b26d633c438cb5adb22f2c30a5cff0Sven Gothel2011-08-311-5/+4
| | | | NativeWindow X11 Error Handler: If quiet do not print message on stderr.
* X11Util.createDisplay() -> X11Util.openDisplay(): Better name match to ↵Sven Gothel2011-08-315-7/+7
| | | | XOpenDisplay/XCloseDisplay
* test script ..Sven Gothel2011-08-311-3/+5
|
* NativeWindow X11 Error Handler: Even if quiet, print message on stderr.Sven Gothel2011-08-311-3/+5
|
* X11OnscreenGLXDrawable: Mark dead GLX_WINDOW code deadSven Gothel2011-08-311-2/+4
|
* glXCreateContextAttribsARB: Use NIO for attributesSven Gothel2011-08-311-22/+27
| | | | Was intended to fix bug 515, which it doesn't. However, NIO usage is fine in this case.
* NEWT/X11 Display: CloseDisplay in same order as creation (ATI); Adding ↵Sven Gothel2011-08-312-26/+55
| | | | | | | | | | | | | | DisplayRelease0; Using 'EDT' suffix for display arguments CloseDisplay in same order as creation (ATI) - This enhanced the erroneous bug 515 (b54497155815852744adb657816cb4057948dae2) situation with closing the display connections. However, some SIGSEGV still slipped through. Adding DisplayRelease0 - Intended for cleaning up resources. Currently a NOP. Using 'EDT' suffix for display arguments - To mark the semantics of the display connection, which may be for window or EDT now.
* Workaround for X11/ATI fglrx bug 515 - Multiple Display ConnectionsSven Gothel2011-08-312-1/+31
| | | | https://jogamp.org/bugzilla/show_bug.cgi?id=515
* DynamicLibraryBundle*: Use generics for better spec - following gluegen ↵Sven Gothel2011-08-319-109/+108
| | | | commit cfb9e118e020707842e6b5136b07f5ab149540c1
* Unit Tests: Remove redundant GLProfile.initSingleton(boolean) callsSven Gothel2011-08-313-13/+0
|
* UnitTests NEWT: Place GLProfile.initSingleton(true) to @BeforeClass method, ↵Sven Gothel2011-08-317-27/+39
| | | | ensuring init after UI Lock
* UnitTests AWT: Remove GLProfile.initSingleton(true) and ensure AWT-dispose ↵Sven Gothel2011-08-3127-79/+70
| | | | | | | | | | | happens on AWT-EDT We will use the default implicit call of GLProfile.initSingleton(false). (This is the same case as for AWT applets as.) We shall create extra test cases for AWT + GLProfile.initSingleton(true) to test it's stability. However .. to nail down our test instability w/ AMD's fglrx driver we move to the default behavior.
* UnitTest UI: SingletonInstance Lock at @BeforeClass - before all other ↵Sven Gothel2011-08-311-2/+2
| | | | sub-class calls
* Test: Cleanup warnings; Add GLProfile.initSingleton(true) call for ↵Sven Gothel2011-08-3011-7/+33
| | | | | | | | | | fluctuating NEWT tests Add GLProfile.initSingleton(true) call for fluctuating NEWT tests - Some of these tests even fail in the <init> state, i.e. cause a JVM stack dump around an early GLX createContext method only when issued via Jenkins. The Ubuntu 11.04/64bit Jenkins node runs 2 nodes (32 and 64 bit). TODO: Find cause.
* TestFocus01SwingAWTRobot: Run AWT destruction on AWT-EDTSven Gothel2011-08-302-12/+18
|
* TestGLDebug*: Remove Thread.dumpStack() ..Sven Gothel2011-08-302-4/+2
|
* TestAWTTextRendererUseVertexArrayBug464: Run AWT destruction on AWT-EDTSven Gothel2011-08-301-4/+13
| | | | | This fixes the _XSend X11 error on GLX commands using AMD driver .. proper cause unknown, but probably a race or condition or threading issue (Display usage by diff threads).
* Cont w/ 5a7811ecd23a3ab1af62b243c82d362431793a57: test-x*.shSven Gothel2011-08-302-4/+11
|
* Use GlueGen's setenv-build-jogl scripts from commit ↵Sven Gothel2011-08-304-29/+15
| | | | 4a75b64107e157ff1db3991cf89bf8d856ddc0e6
* SWT/AWT Test: Run AWT destruction on AWT-EDT, issue shell.close() before ↵Sven Gothel2011-08-301-4/+8
| | | | | | | shell.dispose() This fixes the _XSend X11 error on GLX commands using AMD driver .. proper cause unknown, but probably a race or condition or threading issue (Display usage by diff threads).
* Fix NEWT regression due to fix of bug 502, commit ↵Sven Gothel2011-08-303-9/+17
| | | | | | | | | | | | 9ed513e9a9616f6028084df4c650c8caf31ea49d In case of exessive destroy/create (the NEWT reparenting test cases), some dpyEDT events are slipping through the event dispatcher. This fix uses issues more XSync on both Display connection in case of 'requestFocus' and 'closeWindow'. 'requestFocus' also uses the dpyEDT to issue the XSetInputFocus(..), since it's EDT related.
* Complete commit cb4e73183103c13d8bcf7c7667e1b9ea181e1f5f (sorry)Sven Gothel2011-08-301-4/+4
|
* NEWT Window/WindowImpl: Add generics - addChild()/removeChild() return ↵Sven Gothel2011-08-302-44/+54
| | | | boolean, see Collection::add/remove
* Tests: Comment GLProfile.initSingleton(false), which is redundant / implicit.Sven Gothel2011-08-305-5/+5
|
* ShaderState Usage/Test: Add setShaderState(GL) for pre-use attachment to the ↵Sven Gothel2011-08-305-62/+92
| | | | | | | | | | | GL context ; GLArrayDataClient-GLSL: Check if ShaderState is attached. ShaderState Usage/Test: Add setShaderState(GL) for pre-use attachment to the GL context - test cases utilize ShaderState before useProgram() was invoked, hence we need an API entry to attach the ShaderState explictly GLArrayDataClient-GLSL: Check if ShaderState is attached. - catch error case of non bound ShaderState to GL context
* JAWTWindow.getLocationOnScreen(): Add proper JAWT lockSurface() ; X11Util: ↵Sven Gothel2011-08-303-42/+35
| | | | | | | | | use System.err ; TestParenting02AWT: use GearsES2 JAWTWindow.getLocationOnScreen() - Add proper JAWT lockSurface() - Turns out that the parent location query of a NEWT child to an [J]AWT window didn't lock the window
* Proper classpath for all javah commands, using 'rootrel.build'Sven Gothel2011-08-303-23/+29
|
* Merge remote-tracking branch 'remotes/wwalker/bug_512_no_build_with_Java_7'Sven Gothel2011-08-302-2/+2
|\
| * Fix classpaths to work with Java 7's javahWade Walker2011-08-252-2/+2
| | | | | | | | | | | | Java 7's javah requires all referenced classes to be classpath, even if they're just method parameters and never instantiated. Java 6's version of javah didn't require this.
* | NEWT: Add comment in API doc ; Use more generics in impl.Sven Gothel2011-08-302-7/+9
| |
* | Workaround (Fix) for Bug 502: Multithreading issue w/ libX11 1.4.2 and ↵Sven Gothel2011-08-304-44/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | libxcb 1.7 bug 20708 See https://jogamp.org/bugzilla/show_bug.cgi?id=502 Since the libX11/xcb code doesn't seem to be fixed anytime soon a better usable workaround is required than using a system property to enable 'over locking'. It turns out that the race condition is related to the parallel X11 Display connection usage of GLX/OpenGL and event dispatching. This workaround utilizes 2 X11 Display handles, one for windowing/OpenGL and one for event dispatching. This approach allows us to cont. multithreading use w/o locking the display and works on both implementations, the old bug-free libX11 and the 'new' buggy one. Downside is the little resource overhead of the 2nd X11 Display connection .. well. - Removes the property: 'nativewindow.x11.mt-bug'
* | minor: update script / vsync changes in test w/ 2 windowsSven Gothel2011-08-302-15/+17
| |
* | GLSL DataArray/Handler: Remove ShaderState state and pass it through: ↵Sven Gothel2011-08-3031-353/+668
| | | | | | | | | | | | | | | | | | ShaderState.getShaderState(gl) This removes the dependency of a GLSL GLDataArray object to a specific ShaderState and enables sharing of this VBO data, i.e. via a shared context. Test: TestSharedContextVBOES2NEWT
* | Update README.txt and REPOSITORIES.txtSven Gothel2011-08-242-7/+21
|/
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-27 20:06:11 +0000