Yes... but doesn't util.Timer already use a single thread? If so, then i think it would be correct for each component to instantiate a swing.Timer - as long as that timer, "inside", is using a single thread at its back-end.
I also think that, at Sun's docs, the swing.Timer doesn't have a sharedInstance() method, which i suppose it means it shouldn't be a singleton. Cheers, J.V. 2005/11/10, David Daney <[EMAIL PROTECTED]>: > The documentation in Sun's jdk strongly implies that all > javax.swingTimers share a single thread. Any implementation that does > not do this should be viewed with a great deal of suspicion. > > David Daney. _______________________________________________ Classpath mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath
