Canvas painting and the AWT Dispatch Thread
I'm confused. The code in the BufferStrategy API docs
shows a Window being created and an animation painted _not_ from the AWT dispatch thread.
I followed this pattern to implement my own animation in a Canvas. Canvas.paint() and Canvas.update() are overridden to do nothing. A separate thread repeatedly paints the BufferStrategy back buffer and then call BufferStrategy.show(). FWIW, the Canvas is in a Cardlayout and the thread only starts when the Canvas is selected.
It works great on a collection of test machines. But my app needs to be robust for 10's of thousands of machines, hardware unknown. Not much margin for error.
Now I find warnings in various places never to draw in anything but the AWT EDT.
So are the docs bogus? Or have I misread them? Or is continuous animation an exception to the EDT rule?