Hi Roman,
On Sat, Feb 10, 2007 at 01:31:54PM +0100, Roman Kennke wrote:
> > > 2. Since JDK5 the GC methods have variants for accepting a transparency
> > > value. What if the transparency requirements can't be met? For instance,
> > > on my system there is no way that the graphics chip can render into a
> > > translucent bitmap. The best thing I can do is software rendering.
> >
> > If user requested an accelerated image (via ImageCapabilities),
> > and you can't fulfill the request, then AWTException should be thrown.
> > In other cases you can return an unaccelerated image (essentially a
> > BufferedImage disguised as VolatileImage).
>
> What is confusing me now is that the peer interface (I know it's no more
> official, but still.. at least we Classpathlers stick with it as far as
> we can) for Component doesn't seem to have a
> createVolatileImage(int,int,ImageCapabilities) variant (at least the
> compiler doesn't complain about when I try to make an implementation
> without any such method). How are the capabilities supposed to be
> checked? Or is this actually not checked at all?
Well, a Component have a GraphicsConfiguration associated with it,
so you can find out about the capabilities, and also create
a VI with caps.
It's a bit more complicated than that, but that's the idea.
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".
