Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think you premonition is right, you need to adhere to Swing threading rules. </p> <p>So what to do?</p> <p>First, I am not sure how your app is designed exactly. You say that you have a main frame with a bunch of rows, and potentially each could potentially call one of 9 classes, and they all look like the one above. It seems that these classes will generate their own <code>JFrame</code>. I guess that this new frame is solely used for the progress bar. I will assume that this is the design and will suggest accordingly.</p> <p>I suggest that you perform a couple actions in instances of <code>Runnable</code>, and you drop those <code>Runnable</code> instances into <code>SwingUtilities.invokeLater</code> to have them run on the EDT. At the same time, I would take the time to reorganize your code for ease if reading.</p> <ol> <li>move the creation of your GUI bits into a method: </li> </ol> <pre>public void createComponents () { SwingUtilities.invokeLater(new Runnable() { public void run() { //Create all components progressFrame = new JFrame("Calculation Progress"); progressFrame.setSize(300, 100); pane = progressFrame.getContentPane(); pane.setLayout(null); progressFrame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE); progressBar = new JProgressBar(0, iterations); //Add components to pane pane.add(progressBar); //Position controls (X, Y, width, height) progressBar.setBounds(10, 10, 280, 20); //Make frame visible progressFrame.setResizable(false); //No resize progressFrame.setVisible(true); } }); } </pre> <ol> <li>Then I would methodize the two GUI actions that you have in your calc:</li> </ol> <pre> private void updateProgressBar(final int i) { SwingUtilities.invokeLater(new Runnable() { public void run() { progressBar.setValue(i); //no need for the following //progressBar.repaint(); } }); } private void killDialog() { SwingUtilities.invokeLater(new Runnable() { public void run() { progressFrame.setVisible(false); } }); } </pre> <ol> <li>Finally, replace where the code contained in these new methods with calls to the methods.</li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POCan a progress bar be used in a class outside main?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USakf
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks a lot for your help, I've been stuck on this one for a while. I've been working on it, but I can't figure out how to call the new methods in real time. With my updated code, the GUI is created, and the progress bar is updated after the calculations are performed. Would you mind helping me out with calling the methods? I have everything called similarly within "runCalcs" as follows: SwingUtilities.invokeLater(new Runnable() { public void run() { createComponents(iterations); } });
      singulars
      1. PO
      1. USuser568422
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload