While all that is true, the OP's description of being able to see
each individual component paint is way beyond a subjective
interpretation of performance. Something is broken.
Especially when it happens both in Swing-based Netbeans and in SWT-
based Eclipse. The two environments have essentially no GUI code in
common, so suspicions of one LAF or another being a culprit are
belied by LAF-less Eclipse.
Some version numbers for the OP's Netbeans and Eclipse might be
useful. As would info on what other apps are running at the same
time. Eclipse uses a lot of RAM, and if the OP's black MacBook
starts swapping, that could be a big speed hit. As already
mentioned, a little time spent with Activity Monitor could be very
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden