| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
- Quaternion.isEmpty()
- Texture.dispose(GL)
- GLContext.getGLVersionMajor() / ..Minor()
- GLContextImpl.bindPbufferToTexture() / releasePbufferFromTexture()
- MouseEvent.getWheelRotation()
-
|
|
|
|
| |
doc.
|
|\ |
|
| |
| |
| |
| | |
via isDriverMesa)
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently, the compatibility context on Mesa >= 9.1.3 seems to be
very broken. The core contexts, however, seem to be quite stable. This
commit both reduces and widens the scope of the current Mesa quirk to
include only Compatibility contexts on OpenGL > 3 || 3.n where n >= 1.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
and CR/ENTER are printable for NEWT KeyEvent and font handling. Fix regression.
- Original behavior was treating CR/ENTER them as printable, lets keep it this way.
- KeyEvent: Query these 3 whitespaces upfront, no need to incl. them in 'nonPrintableKeys'.
- Fix regression: Native VK_ENTER was not change in commit 4c34f5980bddcdc84b10cb3bcbb96b365b9d471e.
|
| |/
|/|
| |
| | |
propagating event to show whether it has been consumed.
|
| |
| |
| |
| |
| |
| |
| | |
entry to set/get texture unit (default 0).
Allowing a user to set a specific texture-unit and to query the used texture-unit,
allows one to avoid a collision w/ own texture programming .. i.e. removes the burden to setup all params etc.
|
| |
| |
| |
| | |
due to lot's of confusions.
|
| |
| |
| |
| | |
names, e.g. Version31 -> Version310. ; Trim GLVersionNumber string.
|
| |
| |
| |
| | |
texture alpha properly (pre-multiply), due to lack of ALPHA_BLENDING.
|
| |
| |
| |
| | |
https://code.google.com/p/pngj/
|
| | |
|
|/
|
|
| |
view and 'font-definition' view. ENTER not. Fix ENTER code: 0xa -> 0xd !
|
|
|
|
|
|
|
| |
some X11 tests systems, artifacts could be experienced.
X11 Test systems w/ AMD fglrx and Intel Mesa, the rotated height
is cut off .. probably due to bug of driver code and rotation.
|
|
|
|
| |
keyCode is 0.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug 770:
X11Window.c:
- Request focus _before_ enabling EWMH flags (fullscreen or above) after resize
and temporary invisibility.
This actually allows us to keep the focus after resize and repositioning!
- Set _NET_WM_BYPASS_COMPOSITOR implicit analog to _NET_WM_STATE_FLAG_ABOVE
- Clean up _NET_WM_* flag names, avoiding name space collisions, i.e. adding FLAG!
- Remove dead _NET_WM_STATE setting via direct window property (not working anyways)
- Remove dead code: FS_GRAB_KEYBOARD
X11/WindowDriver.java:
- Enable _NET_WM_STATE_FLAG_ABOVE temporarily if
FLAG_IS_FULLSCREEN && !FLAG_IS_ALWAYSONTOP
- Override focusChanged(..) to react on focus lost/gained
in case of temporarily enabled _NET_WM_STATE_FLAG_ABOVE.
If focus is lost, disable _NET_WM_STATE_FLAG_ABOVE,
otherwise re-enable it.
WindowImpl.java:
- FullscreenAction.run: Always use 'FLAG_IS_FULLSCREEN_SPAN'
+++
Bug 771:
WindowImpl.java:
- Keep fullscreenMonitors and fullscreenUseMainMonitor values intact,
allowing them to be tracked. Remove duplicates in FullscreenAction class.
- MonitorModeListenerImpl.monitorModeChanged:
Add fullscreen path: If the changed monitor is part of fullscreenMonitors,
recalculate the viewport union and reset position and fullscreen-size.
- MonitorModeListenerImpl: Try to regain focus after successful mode change.
|
| |
|
|
|
|
|
|
|
| |
happen at actual native create and destroy.
.. otherwise usage of Screen.createNative() and a later Window creation would cause
the ScreenMonitorState having 2 added listener - which in turn disables it's orig mode reset at Screen destruction.
|
| |
|
|
|
|
| |
temp. display connection!
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
MonitorMode* ; Sort List<MonitorMode> in descending order to be well determined.
Add Comparable<?>: Point*, Dimension*, Rectangle*, SurfaceSize* and MonitorMode*:
- Compare square values
- See API doc for order of special semantics (flags, rotation, ..)
Sort List<MonitorMode> in descending order to be well determined:
- Removes order by native mode id, give user a reliable natural order.
|
|
|
|
| |
like to compare float values - remove 64bit conversion.
|
| |
|
|
|
|
| |
to class header.
|
|
|
|
| |
to class header.
|
|
|
|
| |
Window/Linux ..
|
| |
|
| |
|
| |
|
|
|
|
| |
traversal validation checks.
|
|
|
|
| |
traversal validation checks.
|
|
|
|
| |
case instead.
|
|
|
|
| |
blocking.
|
|
|
|
| |
shutdown. DisplayImpl.shutdownAll(): Don't block.
|
|
|
|
|
|
| |
(NewtCanvasAWT, ..)
.. otherwise an auto repeated key would cause fast focus traversal, not intended.
|
|
|
|
|
|
|
| |
traversal validation checks.
- Remove Frame lost detection
- Allow to have NEWT and it's NewtCanvasAWT claiming to have the focus
|
| |
|
|
|
|
|
|
| |
GLDrawable on Windows.
FIXME: Validate against EGL surface creation: ANGLE uses HWND -> fine!
|
|
|
|
|
|
| |
Robot.waitForIdle() calls.
See commit 8f3b2a4cc14be60681a7bfae0507655cc5702836
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
before certain robot ops.
We have experienced that w/o utilizing AWT components, i.e. NEWT tests,
the AWT-EDT 'sometimes' dies.
Performing AWT robot's waitForIdle() in this situation causes a deadlock,
since the call will never complete it's EventQueue.invokeAndWait() call.
While analyzing this issue, we created a test tool whether the the AWT EDT is still alive.
This test issues EventQueue.invokeLater( .. { flag=true; } ); and polls up until 2s
for the result.
Turns out that the sporadic AWT-EDT issues are solved by this test itself,
i.e. it probably cause it to be reinstated. (?!)
We have to observe this behavior.
Another proof that quantum mechanic rules also apply in the macro cosmos :)
|
| |
|
|
|
|
| |
frame close on current thread ..
|
|
|
|
|
|
| |
GDI would be returned and neither ES1 nor ES2 features are available.
Fixes commit 3e528a69db38711c789a08d1d7335e5a7739f780
|
|
|
|
|
|
|
| |
be returned!
We still have to solve the GL renderer selection / probing problem, i.e. in such cases
we don't know before context realization which GL renderer we actually receive.
|
| |
|
|
|
|
| |
component method.
|
|
|
|
| |
while analyzing)
|