> I can see how this would be faster; once you start doing transformations
> and other advanced effects on the images, we have general-case loops
> that handle those operations. I don't know anything about your application,
> but if it's possible to rotate and then cache the result, you could
> take advantage of the API more. For example, if you are rotating a static
> image in a set number of positions, you could do each rotation once and
> then store each as an image to be used the next time you need that rotation.
This was actually one of the first things I tried, when optimizing my
class. The problem was that java_vm swallowed all my ram and swap space
during the for loop, that contructed the pre-rotated images, and I had
to login remotely and kill X, as nothing was really working... I could
get the for loop working by rotating the picture with intervalls of 36
degrees, but doing it with intervalls of < 10, made my computer crawl.
> Hmmm. Casting objects to different types? Sounds like the Java
> police would be after you.... I don't think this kind of feature would
> make it into the language anytime soon (I don't know what is planned, but
> type-safety and prevention from the dangers of C tricks seem to be
> pretty big goals of the language so far...)
So it seems it's quite "unjavaish"...
===========================================================================
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".
