I have a Swing Applet wherein I create NO new threads.
There are no time-consumptive things occuring.
I create an Applet which has a couple of JTables on it. The data therein is
NOT very extensive.
However, frequently, the applet seems to NOT repaint - whether being
displayed in a browser or in NetBeans AppletViewer.
For the life of me, I cannot see what might be causing this. It does not
appear hardware-specific as it happens on all machines.
Has anyone ever experienced such a thing? Anyone with any ideas what I ought
to be looking for? Thanks, Ike
hiwa - 21 Dec 2003 02:23 GMT
> I have a Swing Applet wherein I create NO new threads.
>
[quoted text clipped - 11 lines]
> Has anyone ever experienced such a thing? Anyone with any ideas what I ought
> to be looking for? Thanks, Ike
Does you applet call the repaint() method explicitly in the start()
method, assuming all the GUI are instantiated in the init() method?
Dave Glasser - 21 Dec 2003 23:58 GMT
"Ike" <rxv@hotmail.com> wrote on Fri, 19 Dec 2003 21:01:02 GMT in
comp.lang.java.gui:
>I have a Swing Applet wherein I create NO new threads.
>
[quoted text clipped - 11 lines]
>Has anyone ever experienced such a thing? Anyone with any ideas what I ought
>to be looking for? Thanks, Ike
I've found that a lot of the difficult-to-solve repaint problems I've
encountered can usually be solved by passing the component that needs
repainting to RepaintManager.addInvalidComponent(). For example, if
you're referring to the component with a reference named "comp", you
would do:
RepaintManager.currentManager(comp).addInvalidComponent(comp);

Signature
Check out QueryForm, a free, open source, Java/Swing-based
front end for relational databases.
http://qform.sourceforge.net