Shoot, I figured it out about an hour after I posted, and couldn't get online
until now.
As a footnote, on Windows
GraphicsDevice.getDefaultConfiguration().getBufferCapabilities().isFullScreenRequred()
returns true. That was what finally clued me in to the problem.
[Message sent by forum member
Well, if he were to just change JFrame to Frame (no
lightweight/heavyweight issues), it still wouldn't work because of
the (fullscreen/BufferStrategy-related) bug. But anyway, the
workaround is indeed to ditch Canvas.
Thanks,
Dmitri
Java2D Team
On Tue, Jul 25, 2006 at 04:43:47PM
Damn it, I was just about to chime in with the exact same fix!
Yeh ditch the canvas thing completely. Just use the original frame.
[Message sent by forum member 'fred34' (fred34)]
http://forums.java.net/jive/thread.jspa?messageID=136539
==
Hi there,
> Stupid question time. :-)
Not so stupid, actually. This is because of our bug, which I happy
to report was fixed in mustang.
To work around it, don't use Canvas, just create the BufferStrategy
off your frame.
Also, you might want to use Frame instead of JFrame - you don
Hello,
Stupid question time. :-)
Why does the following code (correctly) display a black screen with white
numbers under Linux, but just grey under Windows XP? Tested on Java 1.4 and 5
under Windows, Java 1.4, 5, and 6 under Linux (it even works in Kaffe!).
I know I'm missing something obvious
On Mon, 2006-07-24 at 12:27 +0100, Peter B. West wrote:
> Doug noted earlier that the implementation supports 0x200C (ZERO WIDTH
> NON-JOINER) and 0x200D (ZERO WIDTH JOINER). Not supported (along with
> ZWSP) is WORD JOINER 0x2060. I assume this means that neither will ever
> occupy any rendering s
