|
 | make/scripts/tests.sh (diff) |
 | src/test/com/jogamp/opengl/test/junit/jogl/swt/TestBug1421NewtCanvasSWTPosInTabs.java |
|
 | make/scripts/tests.sh (diff) |
 | make/scripts/tests-win.bat (diff) |
 | src/test/com/jogamp/opengl/test/junit/jogl/swt/TestBug1421NewtCanvasSWTPosInTabs.java (diff) |
 | make/scripts/tests-x64-dbg.bat (diff) |
Commit
9512a4bbda02002d06fcbb34504c3bea9c7abdc8
by Sven GothelBug 1421, Bug 1358, Bug 969, Bug 672: Generalization of test case TestGLCanvasSWTNewtCanvasSWTPosInTabs (1/2)
Testing the TabFolder and a SashForm in the 2nd tab covering both SWT layout use cases on both out SWT support classes SWT GLCanvas and NewtCanvasSWT.
Merging TestBug1421NewtCanvasSWTPosInTabs + TestBug672NewtCanvasSWTSashFormComposite into TestGLCanvasSWTNewtCanvasSWTPosInTabs.
TestBug672NewtCanvasSWTSashFormComposite exposes that SWT GLCanvas still requires work for proper High-DPI scaling on OSX!
|
 | src/test/com/jogamp/opengl/test/junit/jogl/swt/TestBug1421NewtCanvasSWTPosInTabs.java |
 | src/test/com/jogamp/opengl/test/junit/jogl/swt/TestGLCanvasSWTNewtCanvasSWTPosInTabs.java |
 | src/test/com/jogamp/opengl/test/junit/jogl/swt/TestBug672NewtCanvasSWTSashFormComposite.java (diff) |
|
 | src/nativewindow/classes/com/jogamp/nativewindow/swt/SWTAccessor.java (diff) |
|
 | src/jogl/classes/com/jogamp/opengl/swt/GLCanvas.java (diff) |
 | src/nativewindow/classes/jogamp/nativewindow/macosx/OSXUtil.java (diff) |
 | src/nativewindow/native/macosx/OSXmisc.m (diff) |
|
 | src/jogl/classes/com/jogamp/opengl/swt/GLCanvas.java (diff) |
 | src/newt/classes/com/jogamp/newt/swt/NewtCanvasSWT.java (diff) |
|
 | src/test/com/jogamp/opengl/test/junit/jogl/swt/TestGLCanvasSWTNewtCanvasSWTPosInTabs.java (diff) |
 | make/scripts/tests.sh (diff) |
|
 | src/test/com/jogamp/opengl/test/junit/jogl/swt/TestBug672NewtCanvasSWTSashFormComposite.java |
 | make/scripts/tests-win.bat (diff) |
 | src/test/com/jogamp/opengl/test/junit/jogl/swt/TestBug672NewtCanvasSWTSashForm.java |
 | make/scripts/tests.sh (diff) |
|
 | make/lib/swt/cocoa-macosx-x86_64/src.zip |
 | make/lib/swt/gtk-linux-x86_64/src.zip (diff) |
 | make/lib/swt/gtk-linux-x86_64/swt.jar (diff) |
 | make/lib/swt/cocoa-macosx-x86_64/about_files/mpl-v20.txt (diff) |
 | make/lib/swt/gtk-linux-x86_64/about_files/mpl-v20.txt (diff) |
 | make/lib/swt/win32-win32-x86_64/swt.jar (diff) |
 | make/lib/swt/cocoa-macosx-x86_64/swt.jar (diff) |
 | make/lib/swt/README.txt (diff) |
|
 | src/nativewindow/classes/jogamp/nativewindow/macosx/OSXUtil.java (diff) |
 | src/nativewindow/native/macosx/OSXmisc.m (diff) |
|
 | src/newt/classes/com/jogamp/newt/swt/NewtCanvasSWT.java (diff) |
|
 | src/newt/classes/com/jogamp/newt/swt/NewtCanvasSWT.java (diff) |
|
 | src/newt/classes/jogamp/newt/WindowImpl.java (diff) |
Commit
141fa0fba0f47851f20acfcb078e11659ebc74cc
by Sven GothelBug 1421: Tackle wrong position of TabFolder, SashForm etc
getClientArea() on MacOS produces a 'difficult' result regarding the position, which usually is returned as zero. Using a zero position issues the bug w/ SashForm, where the offset doesn't seems to be covered by the native NSView nor an SWT parent Composition.
Then using the getLocation() as is (i.e. the view's frame position) may also cause issues with the TabFolder, as it includes the tab's trimming. Here the native NSView 's position includes the tab's trimming, gladly the parent (TabFolder or a Composition)'s clientArea includes this offset.
Therefor, as a testbed - on OSX, getClientArea2(..) returns - position: getLocation() - getParent().getClientArea().position - size: getSize()
This at least works OK'sh using - no special layout parent - TabFolder - SashForm
++++
Unit test TestGLCanvasSWTNewtCanvasSWTPosInTabs: Adding 'addComposite' to test matrix. 'addComposite' wraps our GLCanvas or NewtCanvasSWT into a Composite instead of adding it directly into the layouting parent.
It demonstrates an issue with the new test 'test32_NewtCanvasSWTTabSashGLWComp', i.e. the NewtCanvasSWT is shown on the left as the SashForm's offset is being dropped.
Summary: - No more issues with High-DPI pixelScale observed!
- GLCanvas is being most well layouted, no issues in tests
- NewtCanvasSWT may show severe positioning issues -> test32_NewtCanvasSWTTabSashGLWComp - NewtCanvasSWT always shows a small positioning offset into the lower-right corner w/ overlapping - NewtCanvasSWT overall positioning is not perfectly understood - NewtCanvasSWT misses to hide the NEWT child when changing tabs in TabFolder
|
 | src/test/com/jogamp/opengl/test/junit/jogl/swt/TestGLCanvasSWTNewtCanvasSWTPosInTabs.java (diff) |
 | src/newt/classes/com/jogamp/newt/swt/NewtCanvasSWT.java (diff) |
Commit
557f3d57cc2ca60678fe87df4b4a9c99c016e575
by Sven GothelBug 1358: Merely simplifying the non MacOS getClientAreaInPixels() code path
This also demonstrates that on non MacOS, SWT's scale-factor is artificially imposed on the actual pixel-units, as SWT's getClientArea() is simply returning: DPIUtil.autoScaleDown(getClientAreaInPixels())
|
 | src/newt/classes/com/jogamp/newt/swt/NewtCanvasSWT.java (diff) |