aboutsummaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Destruction of GLAutoDrawable shall not remove them from AnimatorControl ↵Sven Gothel2011-09-0811-144/+121
| | | | | | | | | | | | | | | | | | | (due to recreation) ; NEWT/Window: Remove isValid() API entry - always true! Destruction of GLAutoDrawable shall not remove them from AnimatorControl (due to recreation) - Completes commit b65e1e76d413b70e5593173e6bd36d30675554a6 - WindowImpl: - volatile: windowHandle/visible fields (memeory sync critical) - destroy must set visible := false, to avoid immediate recreation via a display call of another thread, ie an animator. NEWT/Window: Remove isValid() API entry - always true! - NEWT/Window's can always be recreated. - redundancy in API is even worse than redundancy in impl. :)
* Minor edits/cleanup: unused var, finalSven Gothel2011-09-072-2/+1
|
* Revert 98f9eef8279680a7fbd3fccb5840381faf1d5c01: removeNotify makes NEWT ↵Sven Gothel2011-09-071-0/+1
| | | | child invisible again
* Fix commit e1ecd85a9d5877861cde35baababb298d1339898 - send resize eventSven Gothel2011-09-071-4/+17
| | | | | | | Completes fix 2934c9814daf7ae053c3f03957961a2e62125aee Turns out it's more safe to send out the resize events to the listener, since the native event messaging is not reliable in some cases.
* Fix commit e1ecd85a9d5877861cde35baababb298d1339898 - send resize event on ↵Sven Gothel2011-09-071-0/+1
| | | | ScreenMode Change
* ScreenImpl: Debug - drop stack dumpSven Gothel2011-09-071-1/+0
|
* NewtCanvasAWT: setNEWTChild() shall not be public - removeNotify shall not ↵Sven Gothel2011-09-071-4/+3
| | | | make NEWT child invisible (?)
* GLWindows Lifecycle Destroy: Don't remove itself from animator-ctrl - ↵Sven Gothel2011-09-071-7/+1
| | | | recreation is possible
* NEWT/Window: Cleanup Actions: Reparenting, Fullscreen and DecorationSven Gothel2011-09-075-89/+163
| | | | | | | | | | | | - don't assume size/pos change - hence don't set window's values, but wait for satisfaction - don't send resize events on our own, just rely on the event mechanism - fullscreen: don't wrap action around invisibility from Java, Win7 flashes otherwise. Clients who benefit from it (X11) impl. it natively. - fullscreen exit: validate pos/size in case of a child window, like reparenting. Otherwise the container might gets confused (eg. AWT).
* NEWT/ScreenMode: setCurrentScreenMode() shall only act if new mode differs; ↵Sven Gothel2011-09-062-9/+23
| | | | | | | | | On X11 use Thread.sleep(), more cooperative. In case newMode == currentMode, this caused an error, since X11 would never receive mode change events. Thread.sleep() is nicer for the X11/WM .. cooperative multitasking :)
* NEWT/WindowsWindow: call sizeChanged() if invisible as wellSven Gothel2011-09-061-5/+2
| | | | no reason to supress this information, it's sent only once (like X11)
* NEWT/X11Window: Remove unused 'windowReparented()' callback; Remove ↵Sven Gothel2011-09-062-21/+4
| | | | redundant DBG_PRINT on _NET_FRAME_EXTENTS
* NEWT Cleanup: Remove DEBUG_WINDOW_EVENT, ..Sven Gothel2011-09-065-10/+13
|
* Test ScreenMode: Minor changes - less wait/timingSven Gothel2011-09-063-12/+27
|
* Fix test case for commit 68f5a97ef165a39769040e36114c572c7d0f1abdSven Gothel2011-09-061-3/+1
|
* X11Util/Display Lifecycle: Reuse pending (unclosable) Display connectionsSven Gothel2011-09-061-46/+83
| | | | | | | 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
* NEWT: Sync User-LifecycleSven Gothel2011-09-062-10/+15
| | | | | | Sync User-Lifecycle: Display, Screen: createNative(), destroy(), isNativeValid() sync on instance (used by multiple threads)
* NEWT/X11Screen::setCurrentScreenMode: Use device's 'user' Display connection ↵Sven Gothel2011-09-061-6/+7
| | | | instead of on-the-fly temp one
* NEWT/ScreenMode: Remove Cloneable on Immutable .. makes no senseSven Gothel2011-09-062-15/+17
|
* _NET_FRAME_EXTENTS: Remove annoying Warning message. 1 Compiler warningSven Gothel2011-09-061-4/+4
|
* NEWT/Window/Insets: Implement proper Inset usage ; Cleanup ↵Sven Gothel2011-09-0620-472/+610
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* NativeWindow/NEWT: Cont. refinement of Insets usageSven Gothel2011-09-063-9/+21
| | | | Completes commit d4670328991c02a6f11f8873ea7a2331f17d0ef0
* NativeWindow/NEWT: Refine Insets definition for size and position, read and ↵Sven Gothel2011-09-0416-140/+219
| | | | write access
* Unify Immutable/WriteCloneable Usage ; Remove Clonable for ImmutableOnly typesSven Gothel2011-09-0410-33/+30
|
* NativeWindow: Add new Insets/InsetsImmutableSven Gothel2011-09-042-0/+161
|
* Remove prev. Insets implSven Gothel2011-09-041-112/+0
|
* WindowsDWM: Check all methods for availability - Cleanup headerSven Gothel2011-09-042-9/+2
|
* Test Multisample/Translucency: Remove implicit alpha settingsSven Gothel2011-09-042-1/+6
| | | | see commit 3ea949b6a14c1ba631cb41b7439af86b21db4c05
* Complete translucency support for Win32 - tested w/ NEWTSven Gothel2011-09-045-1/+176
| | | | | | | 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*
* NativeWindow/JOGL: Cleanup Caps doc and implicit related values.Sven Gothel2011-09-042-46/+57
| | | | | | | | | Capabilities setBackgroundOpaque -> setAlphaBits GLCapabilities setOnscreen <-> setPBuffer setSampleBuffers -> setAlphaBits
* Complete translucency support (core w/ X11 (only) - tested w/ NEWT)Sven Gothel2011-09-035-17/+180
| | | | | | | | | | | | | | | | | 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
* Revert commit 8dc31bcaa3ee3a2407d1960ab42d094cac642876: Implicit ↵Sven Gothel2011-09-031-2/+1
| | | | setUndecorated(true) if Capabilities !isBackgroundOpaque(). The original manual logic allows better control
* JOGL/X11GLXGraphicsConfiguration: Query opaque/transparent by XRender ↵Sven Gothel2011-09-031-1/+12
| | | | 'alphaMask' cfg
* NEWT Window: Implicit setUndecorated(true) if Capabilities !isBackgroundOpaque()Sven Gothel2011-09-031-1/+2
|
* NEWT: Respect 'setUndecorated(true)' before native creation (ie. startup w/ ↵Sven Gothel2011-09-023-5/+11
| | | | undecorated window)
* Add GL Version 4.2 in GLContext Query - Add verification via ↵Sven Gothel2011-09-0212-48/+64
| | | | | | | | | | 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
* Test Gears ES1/ES2: Fix shared destructionSven Gothel2011-09-021-6/+19
|
* Test Gears ES1/ES2: Fix lifecycle check (shared gears)Sven Gothel2011-09-022-10/+14
|
* TestParenting02NEWT: Don't move parent window -> lots of WM fighting / ↵Sven Gothel2011-09-021-2/+4
| | | | flickering
* Test GLSLSimpleProgram: Add proper destroy ..Sven Gothel2011-09-021-0/+10
|
* 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 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-011-0/+8
|
* 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.
* 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
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-29 12:18:00 +0000