[EMAIL PROTECTED] wrote:
Thanks for the info.
The problem is that my test app works fine on a modern machine with Vista and non-opaque window mode. On an older machine with XP the app is too slow so the additional eye candy which is provided by the non-opaque window mode should not appear.
That's why a auto-detection if hardware acceleration is supported would be a good feature. The result provided by BufferCapabilities seems to be good enough - I've also tested
What's the hardware on the "older machine"?
You can set J2D_TRACE_LEVEL=4 env. variable in the
command line before starting your app, it will
print out the info on the video board/driver.
[code]
GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice().getAvailableAcceleratedMemory()
[/code]
If -1 is returned no HW-accel is supported - is the result better or equal to
BufferCapabilities? AFAIK all these acceleration things are currently only
supported on Windows - right?
It is supported on other platforms (linux, solaris) if the OpenGL
pipeline is enabled (it's not by default). However, there's no
(easy) way to find out the
amount of available vram with OpenGL, so getAvailableAcceleratedMemory()
will return -1 even if the pipeline is enabled.
So it is better to use buffer/image caps to determine if the
pipeline is enabled.
Thanks,
Dmitri
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
