On Fri, 21 Jan 2000, Nathan Meyers wrote:
-->> By 'background' I meant a Java Frame (Window). So, eg. I have the main
-->> frame of my aplication an a dialog box. Moving dialog makes the main
-->> frame repaint itself. This takes particularly much time. Generally, the
-->> same Java application (both AWT and Swing) performs very poorly under
-->> JDK1.2 RC3. With jdk1.1.x performance is very good.
-->
-->Right. The JDK1.2 Graphics2D performance has lots of problems, one of
-->them being excessive numbers of repaints... especially when you drag
OK, so the next Q. Where do the problems come from? Let's take the
AWT Component class and take a look at show() method:
public void show() {
...
ComponentPeer peer = this.peer;
peer.show();
...
}
If I understand it correctly there is an implementation of ComponentPeer
in libawt.so:
[gmyrek@pauli i386]$ nm libawt.so|fgrep -i ComponentPeer|fgrep -i show
0006e2d0 T Java_sun_awt_motif_MComponentPeer_pShow
When show() is called in Java app. Java_sun_awt_motif_MComponentPeer_pShow
from shared lib is called.
So, it is the new implementation of Java_sun_awt_motif_MComponentPeer_pShow
(or better implementation of AWT) which causes all these problems? Java AWT
sources have not been changed (or should have not been - I did not compared
the sources) between jdk1.1 and jdk1.2, so I run exactly the same bytecode.
If so, why, on earth, was the previous implementation dropped or so
dramatically chaged?
-->The CD-ROM for the book is now online; you can view the contents at
Thanks for hints & links;-))
Marek.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
