-
Bug
-
Resolution: Duplicate
-
P3
-
None
-
6u10
customer had noticed some severe drawing issues. They are using a very old tab-pane library in some of these applets -- it comes from Symantec's (AWT, not Swing based)
SFC classes from Visual Cafe. These applets has worked fine for many years (since
Java 1.1 through Java 6 Update 5 without issue).
The tab drawing is completely messed up in Update 10, though (in build 13 as well --
not test this earlier). The area in which the tabs were to have resided shows a single
vertical grey line near the right of the region -- but the tabs still respond to mouse
clicks (if you can manage to hit what you can't see).
In another applet they still have an unresolved issue wherein they cannot resize the
100%x100% applet by resizing the browser frame *if* they have brought up an editing
frame from this applet prior to the resize attempt. This was identified as most likely
being a case where they were calling Swing APIs from outside the event dispatch thread.
Given that they cannot reproduce the issue in a small test applet. they have not, ho
wever, managed to identify the misbehaved code, though. This leads them to plead for
some sort of special mode, e.g. possibly via assertions, whereby they could easily
ascertain where they are doing the wrong things in the wrong thread.
Both sets of bugs lead them to plead for backwards compatibility in Java GUIs.
If old GUIs must break for clean, fast, new GUI handling, then some sort of
compatibility mode (e.g. via an applet parameter) or some tooling to help fix
incompatible UIs is in order. Having UIs just break between Update 5 and Update 10
without any firm ideas as to why or how to fix them is not good.
Machine configuration is a Dell M60 laptop with an NVIDIA Quadro FX graphics
card with Windows XP.
Attached 3 screenshots showing the issue as compared to the issue not being present
when set either -Dsun.java2d.d3d.onscreen=false or -Dsun.java2d.d3d=false as well
as the trace information on the drivers in question. As requested they updated their
NVIDIA drivers to the latest available from Dell for their cards -- to no avail,
this made no different whatsoever to the results.
SFC classes from Visual Cafe. These applets has worked fine for many years (since
Java 1.1 through Java 6 Update 5 without issue).
The tab drawing is completely messed up in Update 10, though (in build 13 as well --
not test this earlier). The area in which the tabs were to have resided shows a single
vertical grey line near the right of the region -- but the tabs still respond to mouse
clicks (if you can manage to hit what you can't see).
In another applet they still have an unresolved issue wherein they cannot resize the
100%x100% applet by resizing the browser frame *if* they have brought up an editing
frame from this applet prior to the resize attempt. This was identified as most likely
being a case where they were calling Swing APIs from outside the event dispatch thread.
Given that they cannot reproduce the issue in a small test applet. they have not, ho
wever, managed to identify the misbehaved code, though. This leads them to plead for
some sort of special mode, e.g. possibly via assertions, whereby they could easily
ascertain where they are doing the wrong things in the wrong thread.
Both sets of bugs lead them to plead for backwards compatibility in Java GUIs.
If old GUIs must break for clean, fast, new GUI handling, then some sort of
compatibility mode (e.g. via an applet parameter) or some tooling to help fix
incompatible UIs is in order. Having UIs just break between Update 5 and Update 10
without any firm ideas as to why or how to fix them is not good.
Machine configuration is a Dell M60 laptop with an NVIDIA Quadro FX graphics
card with Windows XP.
Attached 3 screenshots showing the issue as compared to the issue not being present
when set either -Dsun.java2d.d3d.onscreen=false or -Dsun.java2d.d3d=false as well
as the trace information on the drivers in question. As requested they updated their
NVIDIA drivers to the latest available from Dell for their cards -- to no avail,
this made no different whatsoever to the results.
- duplicates
-
JDK-6694230 D3D/OGL: Incorrect drawing behavior w/ 1.6u10 for components with overridden getInsets()
- Closed