| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
https://jogamp.org/bugzilla/show_bug.cgi?id=517
- Adding some Windows DWM entries to GDI (manual) for translucency support
- Add translucency setting in WindowsWGLGraphicsConfiguration*
|
|
|
|
|
|
|
|
|
| |
Capabilities
setBackgroundOpaque -> setAlphaBits
GLCapabilities
setOnscreen <-> setPBuffer
setSampleBuffers -> setAlphaBits
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DefaultGLCapabilitiesChooser:
- Add penalty for opaque mismatch: dbl-buf > opaq > stencil
GLGraphicsConfigurationFactory:
- Case no-chooser && has-recommended-idx:
- Only use recommended index if caps is opaque,
otherwise use default chooser to validate translucency
NativeWindow Capabilities:
- transparent default values -> 0
Added NEWT Test: TestTranslucencyNEWT
Added command line translucency/undecorated options for TestGearsES2NEWT
|
|
|
|
| |
setUndecorated(true) if Capabilities !isBackgroundOpaque(). The original manual logic allows better control
|
|
|
|
| |
'alphaMask' cfg
|
| |
|
|
|
|
| |
dcb0cc571298be90d0db7ad00fef835fe5fdc46d)
|
|
|
|
| |
XRenderFindVisualFormat for translucent window config
|
| |
|
|
|
|
| |
undecorated window)
|
|
|
|
|
|
|
|
|
|
| |
glGetIntegerv(GL_MAJOR_VERSION|GL_MINOR_VERSION)
Status (Using 4.2 beta driver):
- Windows NV: Created and verified
- Linux AMD: Creates even non existing ones, 4.2 (available) verification returns 0.0
- Linux NV: Created but verification fails, returns 0.0
|
| |
|
| |
|
|
|
|
| |
flickering
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
-> 0x0
Windows: setPosition was invoking setSize (new size propagation) even w/ nop size,
let WM event wmSize invoke setSize.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Windows/NV)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
|
|
|
| |
NativeWindow X11 Error Handler: If quiet do not print message on stderr.
|
|
|
|
| |
XOpenDisplay/XCloseDisplay
|
| |
|
| |
|
| |
|
|
|
|
| |
Was intended to fix bug 515, which it doesn't. However, NIO usage is fine in this case.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
https://jogamp.org/bugzilla/show_bug.cgi?id=515
|
|
|
|
| |
commit cfb9e118e020707842e6b5136b07f5ab149540c1
|
| |
|
|
|
|
| |
ensuring init after UI Lock
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
sub-class calls
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
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).
|
| |
|