Note that there are some explanatory texts on larger screens.

plurals
  1. USXenoRo
    primarykey
    data
    text
    plurals
    1. COI'm unsure if that is the case. I'd say my GUIs & main are mutually consuming each-other (?). --- The main thread should firstly create a GUI for NTLM authentication (username, password, proxy, workstation and domain), then wait for the user to input that data, and then, consume it by authenticating it's webclient (a "headless browser" that will be used to webscrap whats nessessary). Then, the main thread will start webscraping, and (create) a "status-feedback" GUI will (consuming main's data) keep the user aware of the progress...Similar main<->GUI interactions happen throwout the program.
      singulars
    2. COI don't know if I could achieve a solution using EDT and SwingWorker, but I have the feeling the answer would be a "no"; I'll try regardless tough. --- What I'm facing is a situation where I have a need for many completely different GUIs throwout the program's execution, and between them, a lot of processing-related code. Because of that, I need the main (processing) code in the main method, and the GUIs showing up along it, when they are needed (user input) or proper (status-feedback to user). Problem: How to make main wait GUI while Listeners act as "continue main", not "exec. this code".
      singulars
    3. COYes, it's a JFrame that implements Runnable. As for non-GUI thread, well, extending the Thread class or implementing Runnable are the methods I'm familiar with; If there is a different, more proper way to do it when it comes to GUIs (/JFrames), you be welcome to pointing me the ways! (tutorials and javadocs about it). ^^
      singulars
 

Querying!

 
Guidance

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