When do I use SwingWorker?

[TacoManStan]

I am programming a game loop for my, well, game. Duh. I was originally using threads to control this, but soon discovered that Swing is not thread safe. I was lead to SwingWorker, which does whatever task in the background and then updates it on the EDT. This would be great for something like a progress bar, UI, text etc. I think.

The question is, how would I make the game loop? Should I use a swing timer for the game loop, and then not use SwingWorker at all for updating the actual game? Should I use a SwingWorker that repeats tasking the doInBackground method, and then update with the publish method? I have done some research, and it appears that a swing timer would be the best option, but I also saw in a couple of places to always use swing timers for the game loop.

Thanks for any help.

[doWhile]

A SwingTimer facilitates updating after a certain time period (either once or periodically), so if this is the behavior you need then its appropriate. For what its worth, you can update Swing from a Thread using SwingUtilities methods.

[TacoManStan]

Thanks! About the SwingUtilities... You say "For what it's worth". Does that mean that using SwingUtilities for this isn't standard, but still works? Or is it something I should look into? Being able to use Swing with threads without breaking any "rules" would be very... useful.

Thanks again.

[doWhile]

Thanks! About the SwingUtilities... You say "For what it's worth". Does that mean that using SwingUtilities for this isn't standard, but still works? Or is it something I should look into? Being able to use Swing with threads without breaking any "rules" would be very... useful.

Thanks again.

It means that is a way to update Swing from a Thread, nothing more. SwingWorker was introduced when 1.6 was released, prior to that one had to use on SwingUtilities. Why not try both to see which one fits your task?

[TacoManStan]

Ok, thanks again. I, think I know what I should do, but I am not sure. Everything I am using is with arrays of pixel data, retrieved from a sprite sheet. This data is then added to the correct section of a BufferedImage covering an entire JPanel (the game itself). I was going to make a game loop with a SwingTimer, and then have some threads to calculate the positioning of the pixels, etc. I just don't know where to put them... I don't want to do this wrong. I made the mistake of being to "adventurous" before, and had to re-write everything. (What I am doing now).

So yeah, if you have any tips, that would be great. If it would help, it is a 2D RPG style game based completely off tiles. I truly did try and find this by myself, so if you could point me to a couple links that would explain how to implement game loops with swing instead, that would be great.

Thanks.

[TacoManStan]

still need help with this

[TacoManStan]

Still need help...

[Fubarable]

I'm not sure what your specific question is. Where specifically are you stuck? And usually the more specific the question, the more helpful the answer can be.

[Solarsonic]

You use SwingWorker when you want your GUI to have a thread of its own and not be interrupted, since if you use only Threads then your GUI will become unresponsive at times.