classpath-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[cp-patches] FYI: Some AWT/Swing fixes


From: Roman Kennke
Subject: [cp-patches] FYI: Some AWT/Swing fixes
Date: Tue, 27 Sep 2005 16:09:24 +0200 (CEST)
User-agent: SquirrelMail/1.4.4

Hi,

here come some small fixlets with quite nice effect. Most importantly this
moves the revalidate operation itself into the event thread. This makes
some heavy bulk revalidation request more smooth.

I have run extensive tests against Sun's JDK (I'll commit this as soon I
brought them into shape for Mauve), to make sure this is the correct thing
to do. As it seems, most/all operations that effect the GUI structure,
layout or painting are (should be) performed from the event thread. I
suppose there are some more points in our Swing that have to be tuned like
this.

The overall effect is that our Swing is more responsive in the user
experience.

Also included are some small adjustments to Component.show(),
Component.hide() and JComponent.setVisible(), for which I also prepare
some tests, that I only have to bring in shape Mauve.

2005-09-27  Roman Kennke  <address@hidden>

        * java/awt/Component.java
        (hide): Repaint component before invalidating the parent.
        (show): Repaint component before invalidating the parent.
        * javax/swing/JComponent.java
        (revalidate): Check if we are in the event thread, and if not,
        then queue a self-request in the event thread.
        (setVisible): Repaint the parent and queue a revalidate.

/Roman

Attachment: swing-awt-fixes.diff
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]