Re: [JAVA2D] BufferStrategy not working on Windows?

2006-07-26 Thread java2d
AS a footnote to this, the reason I was using a frame was because I couldn't figure out how to get keyboard focus otherwise. The solution I found was to add the key listener to the parent frame, rather than the window that is drawing. William [Message sent by forum member 'afishionado'

[JAVA2D] BufferStrategy not working on Windows?

2006-07-25 Thread java2d
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

Re: [JAVA2D] BufferStrategy not working on Windows?

2006-07-25 Thread Dmitri Trembovetski
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

Re: [JAVA2D] BufferStrategy not working on Windows?

2006-07-25 Thread java2d
Damn it, I was just about to chime in with the exact same fix! Insert explanantion of canvas being heavy weight and swing not working well with them until Mustang here Yeh ditch the canvas thing completely. Just use the original frame. [Message sent by forum member 'fred34' (fred34)]

Re: [JAVA2D] BufferStrategy not working on Windows?

2006-07-25 Thread Dmitri Trembovetski
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

Re: [JAVA2D] BufferStrategy not working on Windows?

2006-07-25 Thread java2d
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