Hi Graeme,
> > I can make some guesses as to how they were designed that might give
> > better performance. If they store the images in VRAM, then they can
> > take advantage of hardware acceleration for the blits to the screen.
> > The downside is that the Windows APIs for doing this are very limited
> > and so you run into one of two problems, depending on how you
> accomplish
> > this.
>
> Our C++ rendering software uses CreateDIBSection on Win32 to give us access
> to fast blitting and also the individual pixels that
> make up the image. Is there a reason why it doesnt work with Java2D ?
JDK 1.1 also used CreateDIBSection for media/toolkit images. The
images are stored in main memory and not accelerated. This is no
better than JDK 1.2.x storing them in BufferedImages (modulo the
difference in tuning between GDI's software copy routines and our
own which we've worked on for 1.3).
The performance benefit comes from using CreateCompatibleBitmap and
with that function you don't get (direct) access to the pixels...
...jim
===========================================================================
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".
