And that's a good practice. If BufferStrategy is used
it allows for the implementation to use the most effective
platform-specific way of double-buffering as opposed
to copying VI->screen.
Thanks,
Dmitri
Ken Warner wrote:
I use the BufferStrategy as an interface to VolitileImage
and it works great in my applet. I don't make VolitileImage's
directly in my code.
Dmitri Trembovetski wrote:
It would be interesting to find out what was causing
the freeze. Would it be possible to create a small
test case reproducing the issue?
Or if you could just show a piece of code which
was using VolatileImages?
Thanks,
Dmitri
Java2D Team
[EMAIL PROTECTED] wrote:
Excellent Dmitri - thank you. I have it working now though not for a
VolatileImage, I had to use a BufferedImage instead. This is because
using the VI caused my applet to freeze when running inside the
browser even though it runs OK when run inside the Eclipse applet
viewer.
Well I guess that's good enough - it has improved my applet
considerably.
===========================================================================
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".
===========================================================================
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".
===========================================================================
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".
