Skip to main content

Better J3DGraphics2D for Java 1.3.2

1 reply [Last post]
Joined: 2004-03-31

I was wondering what changes were under consideration for the J3DGraphics2D for the new Java3D? I've always found it to be the most difficult to use aspect of Java3D.

Curently, I create a BufferedImage to composite all my 2D drawing and then blit it during the post render step. Unfortunately, if the screen size changes, Java3D tries to 'help' you by automatically scaling the blited image. I'd much rather catch the resize event and rebuild my buffer. Is there a way this can be implemented into the new release?

Also, is there work being done to try to make the J3DGraphics2D more stable and handle more of the AWT functions you'd expect a Graphics2D to have?

Mark McKay

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2004-03-17

We don't plan any improvements to J3DGraphics2D in 1.3.2. I believe that the automatic scaling of the BufferedImage that you are seeing is a bug (Issue 8):

If someone has time to take a look at this, we could probably point them in the right direction.

As for other improvements, what did you have in mind? Remember that no API changes are permitted in 1.3.2 -- anything that requires new API can be considered in 1.4 as long as it doesn't detract from the main goal of getting programmable shaders out quickly.

-- Kevin