Kenneth Sizer wrote:
Just thought I'd toss this out: When discussing "logging windows" there is usually the implied existence of multiple
> threads doing things which generate messages for the log.
In my case, that is definitely so... hence:
If this is the case, remember> to use SwingUtilities.invokeXXX... otherwise, you'll notice periodic update
> anomalies and ther weirdness. Swing controls do not like to be mucked
> with directly by threads other than the GUI event handler thread.
Yep, I learned this lesson the hard way as a result of working on this project (I'm not normally a Swing GUI guy, so this is all learning for me).
It turns out that the "anomalies" you can experience as a result of improperly "mucking" with a Swing control from a different thread include a deadlock that brings the entire program to a screeching halt.
TTYL,
Phil -- Vote Badnarik for President 2004 www.badnarik.org
FREE AMERICA Vote Libertarian www.lp.org
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
