I see, the the issue status from IMAGINGJAVA-8774 os resolved.
Means this, that the next version of apsose.imaging will include the bugfix for it?
@bpetermann
Hi!
Yes, some optimization has been implemented for such a situation. They will be available in the next version 24.8 at the beginning of August.
Talking about your specific case I recommend using the new API for rendering. Please, take a look at an example.
import java.awt.image.BufferedImage;
import java.awt.Graphics2D;
import com.aspose.imaging.Image;
import com.aspose.imaging.awt.GraphicsRenderer;
BufferedImage image = new BufferedImage(300, 300, BufferedImage.TYPE_INT_ARGB);
try (Image wmf = Image.load("some.wmf")) // any image file
{
final Graphics2D graphics = image.createGraphics();
try (GraphicsRenderer renderer = new GraphicsRenderer(wmf, Color.getWhite(), SmoothingMode.HighQuality, TextRenderingHint.ClearTypeGridFit))
{
renderer.render(graphics);
// or with scaling
// renderer.render(graphics, 10f);
}
}
The best way is to initialize GraphicsRenderer only once when you load a new image and then just use GraphicsRenderer.render(Graphics2D, scale) in the paint method of your Swing component.