jogl.git - JOGL repository on http://jogamp.org/ ;

	Commit message (Collapse)	Author	Age	Files	Lines
*	NativeWindow/Newt X11ErrorHandler enhancement / unification - don't throw ↵	Sven Gothel	2012-07-05	1	-23/+58
\| \| \| \| \| \| \| \| \| \| \| \|	exceptions. Handles also XAWT BadMatch X_SetInputFocus. X11ErrorHandler code now dumps proper information about the opcode and error message and the running Java thread. Having propery "nativewindow.debug.X11Util.XErrorStackDump" or "nativewindow.debug=all' set, a stack trace is dumped. Since the X11ErrorHandler may catch an XAWT error: BadMatch X_SetInputFocus, we cannot throw an exception and better keep running.
*	Fix Bug 560 and NEWT window closing behavior in general for all platforms.	Sven Gothel	2012-05-01	1	-3/+6
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	- NEWT/WindowImpl: - 'void windowDestroyNotify()' -> 'boolean windowDestroyNotify(boolean force)', allowing to signal a forced close, as well as replying whether the window has been closed. (called by native code) - destroy(): set states before releasing the window lock - NEWT/X11: Pass windowDeleteAtom for reconfigure window, in case of reparenting child to top-level - NEWT/OSX: - Add 'BOOL windowShouldClose()' impl., ie. having a chance to reject the close attempt - Common impl. for 'windowShouldClose' and 'windowWillClose' -> 'windowClosingImpl' utilizing new 'windowDestroyNotify' code (see above). Fixes bug 560. - NEWT/JOGLNewtApplet1Run: Refine out-of browser window behavior for window-close button - default: move NEWT window back to browser parent - closeable: close NEWT window - jogl-test-applets: Add NApplet-Closeable test (Applet out-of browser window is closable)
*	DEBUG Output: More thread-names to drawable/context lifecycle; Remove ↵	Sven Gothel	2012-02-22	1	-1/+1
\| \| \| \|	massive '!!!' occurence
*	NEWT/X11: Fix regressions of commit ↵	Sven Gothel	2011-12-23	1	-3/+3
\| \| \| \|	f3f794fe37a7e33a771a4a702f3f46ead4dc6d03: Unresolved symbols. Disable VERBOSE.
*	NEWT Multi-Monitor 1/2: Allow negative window position; Validate Screen-Index;	Sven Gothel	2011-12-23	1	-0/+660
	- Allow negative window position, using flag 'autoPosition' to mark a custom user position. This impacts Windows and X11 window creation code, which supports native auto positioning. - Screen: Validate Screen-Index. In 'big-desktop' mode the Screen index is always 0. This is true for X11 with Xinerama enabled and MS-Windows in general. Platforms w/o multiple Screen support always use index 0. - X11: Separate X11 Display/Screen/Window native code in their respective C files - Windows test scripts: use '%*' to catch all arguments - Add missing (c)