… if you want !
http://developer.java.sun.com/developer/bugParade/bugs/4916948.html
Cheers,
Mik
Transformations are not hw accelerated, so i dont use Transformations.
But wait until they accelerate transformations also, maybe then your bug is gone, because transformation is done by graphics hardware and not by software
Yes, that could be correct, but the fix of this bug is very much required NOW for those like me that rely on the subpixel-rendering capabilities of Java2D.
The bug is really simple to fix and I hope to see it fixed in 1.4.1_03
Cheers,
Mik
it’s highly unlikely the fix would make it into _03 release because only escalations are allowed into _xx releases. Typically an escalation won’t be filed for a bug which has a workaround…
Typically an escalation won’t be filed for a bug which has a workaround…
Oh my GOD, I submitted a workaround !! ;D
Come on, Trembovetski, it’s just a quick,quick fix that helps to keep the code clean from those ugly workarounds.
I think that the Batik staff will appreciate the fix very much too.
Cheers,
Mik
Now you know not to ever include workarounds in the bug reports :)… leave them for the public comments that Sun never reads ;D
Sad, isn’t it ?
I’ll take this into account for the next bug ;D
Hey, do you want to see what we’re doing with Java/Java2D ?
goto www.classx.it (Castalia, MoreFX)
A sample video (short) ?
http://www.classx.it/classx_gfx/cst_video0.wmv
Suitable even if you don’t speak italian 
Cheers,
Mik
Hey that looks cool… wish I could read Italian 
Hey, we can figure out a workaround for ourselves =)
of course, the rules aren’t that “no bug with a workaround ever gets escalated”. It’s just that the bar for getting a fix into a _xx release is pretty high.
OK, ok.
At least SUN is aware about the JD2 problem, so thay know what to do…
Did you see our CASTALIA (see my previous post) ?
Mik
[quote]Hey, we can figure out a workaround for ourselves =)
of course, the rules aren’t that “no bug with a workaround ever gets escalated”. It’s just that the bar for getting a fix into a _xx release is pretty high.
[/quote]
I understand… I was just poking fun… considering the scope of the Java APIs and the amount of work involved in maintaining them it makes a lot of sense that you are very careful about what you include in the _xx releases. Programmers expect those releases to be less likely to introduce new problems. Only allowing critical fixes is one way to reduce the risk of breaking stuff.