In order to have this issue "closed" (i.e. answered) here, the result from the comments:
Marco13 : Although I have never encountered such an error, it might be worth trying -Dsun.java2d.opengl=true or -Dsun.java2d.d3d=false
(referring to the VM flags listed at http://docs.oracle.com/javase/7/docs/technotes/guides/2d/flags.html#d3d )
Jason : Adding -Dsun.java2s.d3d corrected the issue.
(I assume that this referred to setting -Dsun.java2s.d3d=false, since it is enabled by default)
Regarding the question from the last comment:
"Do you think there some sort of performance benefit to enabling the Direct3D support (for a data entry application)?"
I have not yet used the d3d
flag, but only the opengl
flag, for some experiments, and not for performance tests. So I don't know in how far this flag noticably affects the performance. Again, my gut feeling is that for simple applications, this should not really have a noticable effect. With "simple", I mean applications that only use standard GUI components, and do not perform complex custom rendering operations via a Graphics2D
in in an overridden paintComponent
method. But according to the screenshot, this application might at least involve the most complex "standard GUI component" that exists in Swing - namely a JTable. So if you have, for example, a large JTable in a ScrollPane, possibly with complex custom CellRenderers, you should consider a dedicated test of the performance impact on some (preferably the slowest) of the target machines, if possible.