JEditorPane setPage() problem

Actually, if you need to wait for the search, I would try something like this:

public void actionPerformed(ActionEvent ae){
        try{
            jep.setPage("file:///c:/Searching.txt");

            validate();
            repaint();

            new Thread( new Runnable() {
                public void run() {
                      String text = jtf.getText();
                      SearchBible2_1 sb = new SearchBible2_1();
                      sb.search(text);
                      jep.setPage("file:///c:/BibleSearchResults.html");
                }
            }).start();
           
        }
        catch(Exception e){
            System.out.println(e.getMessage());
        }
    }  

Hi,
  Thanks Shawn.  The only thing I had to change in your code to get it to run was add try/catch blocks in the nested class but it doesn't write work.  After entering the search string the pane  goes all white for several seconds and then the text from Searching.txt flashes on the pane for just a split second and immediately after the search results are displayed...
   

Guess your search wasn't as slow as you thought!

Thanks,
Shawn

well, I'm not sure what's happening. I've tested it over 100 times so far.  When I start  the program and do the first search, the pane goes white for what appears to be the whole search time...several seconds as I said.  Then Seaching.txt may or may not appear, but for only a split second - then the results appear.  If I continue entering searches I get similar results.  But if I minimize the window and then bring it back up and enter a search, then Searching.txt may come up immediately or at least the duration tat the pane stays blank is greatly reduces.  It seems to have something to do with repainting, though I don't understand what.  
  Perhaps you do?
ps - I'm raising the point value to 500.  Thanks for your time.

>> After entering the search string the pane  goes all white for several seconds

Because this code is in actionPerformed(), it will be run as the result of an AWT event, as is the case with all listeners.  This means that your code runs on the AWT (event-dispatch) thread.

You are having a problem because the code which repaints your window also runs on the AWT thread.  If this code is not given a chance to run, the screen "stays white" for a long time.  This is why it is considered "bad practice" to run any time-consuming code in event listeners.  Any time consuming code should always run on a different thread.

That being said, this is not the only reason the AWT thread would not be given a chance to run.  If you perform some task that will take a long time to complete, and it does not yield to other threads, it could potentially run until completion, halting all other threads (on a single-processor system).  This is likely the case with your search.

The search is probably given a chance to run before the paint event is dispatched, so the window doesn't know that it is supposed to be repainted.

public void actionPerformed(ActionEvent ae){
        try{
            jep.setPage("file:///c:/Searching.txt");
        }
        catch(Exception e){
            System.out.println(e.getMessage());
        }

        myWindow.validate();
        myWindow.repaint(); // this doesn't actually repaint the window, just posts an event.

        new Thread( new Runnable() {
             public void run() {
                  String text = jtf.getText();

                  // make sure event thread has a chance to run
                  Thread.sleep( 100 ); // that should be plenty

                  SearchBible2_1 sb = new SearchBible2_1();
                  sb.search(text);
                  try {
                      jep.setPage("file:///c:/BibleSearchResults.html");
                  } catch(Exception ex) { System.out.println(ex.getMessage()); }
            }
        }).start();
    }


If that doesn't fix the problem with the screen staying white, you may want to have a look at some of your other event listeners, to make sure that they aren't holding up the event thread.

Good Luck,
Shawn

Thanks, Shawn, your last example works great.