> I've never measured the CPU occupation of an AWT app, though; might be
> interesting to run an AWT example and see if it takes up the same amount of
> CPU. If not, then Swing's obviously doing things in the background that an
> AWT app's not. (Maybe just filtering the events through all the event
> listeners?)
CPU usage when running the swing demo is not a good indicator
of whether the use of swing in an application is going to perform
the same way. The demo has lots of whizzy components in it that
are going to eat the CPU. Unfortunately swing does consume lots
of memory. In most cases the memory loss is a known bug and Sun
is working to correct the problem.
--Corey
>
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
/* Corey Brown (WB0RXQ): 20m, 15m, 2m(146.82) 70cm(443.65) */
/* AT&T NCS | [EMAIL PROTECTED] */
/* Alpharetta, Ga 30005 | [EMAIL PROTECTED] */
/* (770)750-8071 | New rays from an ancient sun (JS) */
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
