Back to General and Gameplay Programming

[java] threads

mill-o · 2001-11-14T13:23:08

i'm in the process of learning swing so instead of just writing a GUI that doesn't do anything, i decided to write an application that actually does something. everything works great apart from that i don't know how to use threads. the thing is that one operation "freezes" the gui. i know this can be solved by using threads for the processor hungry operation, just not how. i have these classes: Main // doh GUI // the gui. extends JFrame Application // this is where the calculations are done (more classes, but these aren't important) Main creates a new Application. Application calls the GUI and when the user performs a certain action, a cpu hungry operation performs some calculations. I'd like to run this in a new thread instead of the main thread so that i won't lock up the GUI. any ideas how to implement this or where to find more information? i've checked java.sun.com, but i weren't able to adapt their examples to suit my needs. _______________________________ catch (SpellingException e) {} Edited by - mill-o on November 9, 2001 7:54:46 AM Edited by - mill-o on November 9, 2001 8:26:44 AM

General and Gameplay Programming Programming

Started by mill-o November 09, 2001 06:52 AM

13 comments, last by mill-o 22 years, 5 months ago

mill-o

122

Author

November 12, 2001 01:18 PM

okay.. i did as you suggested and it works, more or less. i wrote a class Progress which can be seen below.

      class Progress {    private int progress;	    public Progress() {        progress = 0;    }	    public int getProgress() {        return progress;    }	    public void incProgress() {        progress++;    }}// --------------------------------------------------------// update progress, in the class that does the calculationsprogress.incProgress();SwingUtilities.invokeLater(new Runnable(){    public void run() {        progressMonitor.setProgress(progress.getProgress());    }});

the thing is that now the whole task takes 17000 ms to complete instead of 8000 ms. is this the price i have to pay or i'm doing something wrong?

______________________________
catch (SpellingException e) {}

Edited by - mill-o on November 12, 2001 2:19:21 PM

Edited by - mill-o on November 12, 2001 2:19:37 PM

_______________________ http://mill.3dfxsweden.net

c_wraith

122

November 13, 2001 04:17 AM

The only thing I can think of is that you''re updating the progressbar a LOT... That''s the only reason that solution should be slower. If you''re updating the bar more than a few hundred times, I''d say it''s worth looking into updating it far less often.

mill-o

122

Author

November 13, 2001 05:36 AM

hehe okay, sounds reasonable. the textfile i''m using to test the program with contains ~200000 lines of text and i''m updating the progress bar in a loop which loops for every line, in other words, 200000 updates

i''ll fiddle a little and post the new results later tonight

_______________________ http://mill.3dfxsweden.net

Neophyte

595

November 13, 2001 08:18 AM

If more than one thread accesses the same instance of your Progress-class you should also make the methods called synchronized.

-Neophyte

- Death awaits you all with nasty, big, pointy teeth. -

mill-o

122

Author

November 14, 2001 01:23 PM

it works great now that i''m only updating two times every second. thanks a lot everyone

_______________________ http://mill.3dfxsweden.net

[java] threads

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

[java] threads

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines