Should I care about BT not available? Or... Is Deep Sleep safe??

Question

As many others here from what I've seen, BT in not available from time to time. I would rather put my MB to sleep rather than shut it down completely. I've downloaded the Deep Sleep Widget and I'm thinking of using this every time BT becomes unavailable. It seems that BT is not available more and more these days.
I don't use BT for anything and I'm wondering if it's safe to use Deep Sleep to put MB to bed each night.
Is it OK to use DS on my MB when BT is MIA?
Thanks

Answer 1

So what does this mean? Does this mean that if I am
going to spawn a thread which updates a Swing
component, that any code which modifies that component
(say setText, or setLocation, etc...), I should wrap
those commands inside Runnable and pass them to
SwingUtilities.invokeAndWait()???If the code that is updating the Swing component is not actually in the Swing thread, then you do have to do that. The Swing thread, by the way, is the one that calls your ActionListeners and other component listeners like them. So you can update Swing components directly from Swing listeners, but otherwise you have to do the invokeAndWait business.
Do I only have to do this if I think there may be
multiple threads accessing the Swing object at the
same thing? I assume so...Yes. And remember that the Swing thread is one of those multiple threads; refer back to the previous comment.
An example I'm dealing with is updating a
JProgressBar. I create multiple threads at startup to
get initial values. These commands take time and it is
much faster to start them all at once rather than run
them sequentially. However, each job then increments
the JProgressBar when it completes. I figured this is
as good example as any of violating this "Thead Safe"
issue, since you have multiple threads trying to
update a single Swing component.Yes, that's a good example.