🚀 go-pugleaf

Nitesh Arora <nitesh.arora@patni.com> wrote:
> HI...

> Thanx a lot for ur suggestion but teh applicatio we have developed doesn't
> use a new thred for printing. What it does is , as soon as the the print
> buttonis clicked, an object of a PRINT pRIVIEW class(created by us) is
> instantiated which issimilar to the normal windows printing screen. Could
> you plz elabborate on the concept u r talking about. Is there some way of
> optimizing SWING code for better and speedy performance.

Right.  Because your app doesn't use a thread for its printing, the repainting
performance is affected.  The JVM itself uses multiple threads and one of
those threads handles painting, but that same thread also handles events.

If you fire an event which then triggers some long-lived process, and don't 
take steps to get that process into its own thread, then everything else
in that thread's workload will be delayed, including SWING's ability to
paint the screen.

Here's a link to sun's threads tutorial:
http://java.sun.com/docs/books/tutorial/essential/threads/definition.html


-- 
Joi Ellis (TeamB) 
No direct email, please.
For best results, post on news server newsgroups.borland.com!