------- Comment #12 from hendrich at informatik dot uni-hamburg dot de 2006-03-07 13:27 ------- As an experiment, I rewrote the Swing-based animation to a pure AWT-based animation (without double-buffering). I tried running with the JDK and jamvm+classpath (with and without the gdk_flush()). Observations:
* the animation shows horrible flickering with the JDK and with classpath: all fillRect() calls are done directly on on-screen buffers. (Obviously, I forgot that double-buffering had to be done manually in the AWT...) * with the gdk_flush() calls after each fillRect(), jamvm+classpath runs even slower than the Swing version. One can literally watch jamvm painting individual rectangles. (The Swing RepaintManager seems to do a good job to coalesce repaints). * jamvm+classpath does NOT call update() but only paint(). This seems wrong. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26486 _______________________________________________ Bug-classpath mailing list Bug-classpath@gnu.org http://lists.gnu.org/mailman/listinfo/bug-classpath