Stuck again - ProgressMonitorDialog this time [message #22342] |
Tue, 29 April 2003 10:40  |
Eclipse User |
|
|
|
Hi,
I have the following code...
try
{
IRunnableWithProgress op = new MyActionDelegate(String);
ProgressMonitorDialog progDiag = new ProgressMonitorDialog(shell);
progDiag.run(true, false, op);
}
catch (InvocationTargetException e)
{
// blah blah
}
catch (InterruptedException e)
{
// blah blah
}
But i just cannot get the dialog to disappear - I've tried setting the
dialog to hte same thread (awful performance,
so do not want to do that anyway) and then using progDiag.close(); - i'm
setting the IProgressMonitor in
MyActionDelegate.run() method to "done()". Can someone please post some
example code that they know
works - all I am after is to regain control of eclipse as I can't make my
dialog close!!
Kind regards (learning eclipse slowly...)
Matt Hawkins
|
|
|
|
Re: Stuck again - ProgressMonitorDialog this time [message #22636 is a reply to message #22461] |
Tue, 29 April 2003 11:54  |
Eclipse User |
|
|
|
Well I think i've sorted it out - there was some deadlock.
If there is anyone who works for IBM, and specifically works on a websphere
component,
then can someone point me at the right place to look for getting a list of
all jar dependencies
out of the component.xml file?
I work for IBM and have already written a wsbld task - trouble is I want to
write the same kind of thing
to work in wsadie/eclipse.
If you could email any kind of info to hawkini_uk@uk.ibm.com.
Cheers!
"Richard L. Kulp" <richkulp@us.ibm.com> wrote in message
news:b8m5c0$7bq$1@rogue.oti.com...
> You're doing the right things.
>
> Is your thread that creates the ProgressMonitor dialog maybe already
> running within another ProgressMonitor dialog? Because in that case it
> won't put up another dialog.
>
> Other than that, bring up in debug mode, and put a breakpoint in your
> code where you are done, and make sure that your runnable returns and
> that it goes through ModelContextThread.run() on return and eventually
> sets "continueEventDispatching" variable to false.
>
> Then break into the main thread and see that it is waiting within
> ModalContextThread.block().
>
|
|
|
Powered by
FUDForum. Page generated in 0.02899 seconds