| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
See commit 9ed513e9a9616f6028084df4c650c8caf31ea49d (bug 502)
Since we cannot close Display connections (X11/AMD), at least we reuse them
to not bloat the memory for long term applications
|
|
|
|
|
|
| |
Sync User-Lifecycle:
Display, Screen: createNative(), destroy(), isNativeValid()
sync on instance (used by multiple threads)
|
|
|
|
| |
instead of on-the-fly temp one
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
WindowImpl::reconfigureWindowImpl
Implement proper Inset usage (window decoration size)
- Insets are either polled (updateInsets()) or event driven (insetsChanged())
- Insets are used for size/pos calculations from Java side
- Natural size/pos in NEWT is client-area, ie w/o Insets
- Adding setTopLevelPosition()/setTopLevelSize() for top-level values,
ie including insets
WindowImpl::reconfigureWindowImpl
- Use flags to pass down the requested action to the native implementation
- Impl. all native actions: visible, decoration, reparent, resize, fullscreen
- Always use size/pos in client-area space, impl. shall use Insets to tranform them
- Remove double-setting of (reparent/fullscreen), which where introduced due to buggy impl. code
- Fix return from fullscreen position: Was overwritten with FS position (0/0)
- Fix decoration change: Remove visible toggle - not required, and actually disturbing
X11Windows/WindowsWindow: Added/Fixed Insets impl.
Tests (manual):
- TestSharedContextVBOES2NEWT utilizies proper window layout using Insets
- TestParenting03bAWT uses window layout for reparenting
|
|
|
|
| |
Completes commit d4670328991c02a6f11f8873ea7a2331f17d0ef0
|
|
|
|
| |
write access
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
see commit 3ea949b6a14c1ba631cb41b7439af86b21db4c05
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
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
|