Originally posted by clio katz:
What sort of high-level design considerations would I need if I had potentially long-running task(s) [with or without a GUI visual cue like a progressMonitor], that I might need to interrupt (*visually*, but not at task-level) due to severe error(s) generated external to the thread?
At the moment, I'm allowing the task to complete before I provide any visual cue about other errors. I do provide app-viewable logs, but I am considering using a status area as well.
Ultimately I'm working around the problem of not being able to reliably _showMessageDialog from any executing thread that may not be immediately "dispatch"able. On the other hand, it may just be poor design (i.e. undesirable) to popup error messages when background tasks fail.
Ultimately I'm working around the problem of not being able to reliably _showMessageDialog from any executing thread that may not be immediately "dispatch"able.
Originally posted by Eddie Vanda:
There are ten screens on a tabbed pane and the user would be quite interested in the first one. It is a booking/notes system and the other screens show further information, so it really only takes about two seconds to get the info for the first screen.
I guess that I need a thread to fetch the information screen by screen and then progressively do invokeLater on each screen's gui to keep the user busy with the first few screens while the later screens are loading.
The system has been operational with about 30 users since the start of this year so I can take a bit longer to get this right. I have solved most of the major problems this year so now I am trying to make it nice without disturbing the code already working.
[ May 17, 2004: Message edited by: Eddie Vanda ]
Originally posted by Don Kiddick:
I don't understand this. In what situations would you not be able to call showMessageDialog ? If you want it to be exectuted synchronously call SwingUtilities.invokeAndWait().
Please can you rephrase your question(s) ?