Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 174
  • Last Modified:

Updating a dialog while reading a file

I have a dialog that starts up a new file reader object (that runs in a separate thread). That file reader object needs to update a textfield message box on the dialog as it progresses through the file. I tried  starting the dialog in new thread but the message box still doesn't update until the file reader object is done reading the file. Here's a code summary of what I have done:

Thread a;
Runnable run2 = new Runnable(){
    public void run(){
        //start up dialog that starts the file reader object (in another thread)
    }
};

a = new Thread(run2);
a.start();

Any ideas how I correctly update the textfield in the dialog from the different file reader object? Right now I pass a reference to the textfield to the file reader object.
0
cmp2
Asked:
cmp2
  • 8
  • 8
  • 6
1 Solution
 
CEHJCommented:
Try something like:


// inner class
class FieldUpdater implements Runnable {
      public static void run() {
            yourDialog.setText("New text");
      }
}


// in your file thread (i.e. in run2) - update dialog:
invokeAndWait(new FieldUpdater())

0
 
CEHJCommented:
Sorry

SwingUtilities.invokeAndWait(new FieldUpdater());
0
 
objectsCommented:
pass a reference to the text filed to your thread:

class MyThread implements Runnable
{
   JTextField TF = null;

   MyThread(JTextField tf)
   {
      TF = tf;
   }

   public void run()
   {
      ...
      // to update text field use:
      // TF.setText(s);
      ...
   }
}
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Mayank SAssociate Director - Product EngineeringCommented:
>> Runnable run2 = new Runnable(){

Thread run2 = new Thread () {

could also work.
0
 
Mayank SAssociate Director - Product EngineeringCommented:
I don't think that my comment would make much of a difference because complete solutions had already been provided. It was just another alternative which didn't make much of a difference.

Split between objects and CEHJ only.
0
 
objectsCommented:
theres no need to use invokeAndWait() in this case.
0
 
CEHJCommented:
True but it doesn't hurt and encourages good habits for when it is required
0
 
objectsCommented:
unnecessaary object creation is *not* a good habit to encourage.
In fact it is a *bad* habit.
0
 
CEHJCommented:
All that will happen, most probably, if the questioner is not aware of the working of interaction with the EDT, is that he'll go away and take the easy way in another context and wonder why he's got problems. It's the correct way to do it anyway as it happens. It just transpires that you can get away without it in this case.
0
 
objectsCommented:
Sorry but thats does not make any sense whatsever, what you have posted is not relevant to this question. And even if they were then you should explain the reasoning (but I guess there is none so whats to explain).
0
 
CEHJCommented:
I've done all the explaining that i'm going to do sorry. If you don't understand what i mean, maybe mayank will be kind enough to explain it to you
0
 
objectsCommented:
Explaination of what??? The point is your comment is irrelevant to the question.
So no explanation necessary.
0
 
Mayank SAssociate Director - Product EngineeringCommented:
Ah, cool it guys. Venabili, for some reason, I feel your initial recommendation was fine and I hope the question is closed as per that ;-)
0
 
objectsCommented:
> for some reason, I feel your initial recommendation was fine

Can you help me understand then how calling setText() from the event dispatch thread will make any difference then?
0
 
Mayank SAssociate Director - Product EngineeringCommented:
>> I feel your initial recommendation was fine

Oh, I said that just hoping to close the arguments going on. I don't see a point arguing so much because the questioner is not listening.

>>  how calling setText() from the event dispatch thread will make any difference

So far, I had not been following the comments carefully on this page after the clean-up comment, but now that I do see them again, I think that the invokeAndWait () should not be used.
0
 
objectsCommented:
>  I don't see a point arguing so much because the questioner is not listening.

My concern in this case is more the PAQ, people reading the thread at a later date will be misled. (I don't see a point in arguing about it either)
0
 
Mayank SAssociate Director - Product EngineeringCommented:
>> people reading the thread at a later date

Your concern about that is correct.
0
 
CEHJCommented:
A point to you mayankeagle - and the last word on the matter from me - i too am concerned, believe it or not, about people being misled. That's why i am pointing out that it's NOT ok to change components from a non-EDT thread in Swing in most cases.
0
 
objectsCommented:
> That's why i am pointing out that it's NOT ok to change components from a non-EDT thread in Swing in most cases.

no one said it was but that has nothing to do with this question.
0
 
Mayank SAssociate Director - Product EngineeringCommented:
I know that you are concerned too, CEHJ ;-) I know that you always are.... both of you :-)

But as far as my knowledge goes, I don't see why invokeAndWait () would help much, and I also don't find what non-EDT thread in Swing has to do with this. Maybe that I know a little lesser or am unable to see something which is very apparent to both of you. Excuse my little knowledge compared to yours ;-)
0
 
Mayank SAssociate Director - Product EngineeringCommented:
Don't be cross at me for something ;-) I hope you didn't miscomprehend me to be partial or something like that.

>> believe it or not,

You don't need to say that. I always believe in what you say.

I respect both of you equally, and your knowledge. Maybe that I don't know enough to speak more on this.
0
 
Mayank SAssociate Director - Product EngineeringCommented:
I would still say, split objects and CEHJ, like I said before. This is the last comment from me on this page.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 8
  • 8
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now