Summary: | Newt canvas in Miglayout fail to resize OR occupy complete JFrame instead of its target layout cell | ||
---|---|---|---|
Product: | [JogAmp] Jogl | Reporter: | Martin <martin.pernollet> |
Component: | opengl | Assignee: | Sven Gothel <sgothel> |
Status: | IN_PROGRESS --- | ||
Severity: | major | CC: | gouessej |
Priority: | P4 | ||
Version: | 3.0.0 | ||
Hardware: | All | ||
OS: | macosx | ||
Type: | DEFECT | SCM Refs: | |
Workaround: | --- |
Description
Martin
2015-10-21 14:58:59 CEST
JRE 1.6? Oracle Java, OpenJDK or Apple Java? I am now using - Oracle JVM 25.40-b25 for Java 1.8.0_40-ea - MacOS Sierra 10.12.3 - Jogl 2.3.2 The downsizing bug problem still exists despite a little different. I reproduce easily with either pure JOGL snippet as well as Jzy3d 1.0 pre-built examples (http://download.jzy3d.org/api/1.0/jzy3d-guide-1.0-demos-exe.zip) A Jzy3d user facing the resize problem confirms he is NOT using MigLayout, so the problem is not related to the UI layout framework. (In reply to Martin from comment #3) > A Jzy3d user facing the resize problem confirms he is NOT using MigLayout, > so the problem is not related to the UI layout framework. We need a simple (w/o jzy3d) standalone test case. Please reopen if bug still persist and reproducable w/ that test case. I walk the bug list currently and I cannot work with the given information. Thank you. Thanks! I actually already left a code reproducing the problem. The exact program to run is located here : https://github.com/jzy3d/jzy3d-jogl-debug/blob/master/src/main/java/org/jzy3d/demos/browser/DemoBrowser.java It shows problems embedding JOGL GLCanvas in a Miglayout application which is explained in the Javadoc. (In reply to Martin from comment #5) > Thanks! > > I actually already left a code reproducing the problem. > > The exact program to run is located here : > https://github.com/jzy3d/jzy3d-jogl-debug/blob/master/src/main/java/org/ > jzy3d/demos/browser/DemoBrowser.java > > It shows problems embedding JOGL GLCanvas in a Miglayout application which > is explained in the Javadoc. Thank you. Hence I reopened it and earmarked for 2.4.0 for the time being. Next step would be to create a unit test with your example, then to fix the issue. |