How to make a Job show the reason why it is blocked? [message #273160] |
Thu, 30 September 2004 18:04  |
Eclipse User |
|
|
|
A User Job is very nice in that it shows a Progress Dialog and gives the
user the option to run it in the background. However, if the User Job
cannot be scheduled immediately because of schedule rule conflicts, it
doesn't put out a dialog that shows the reason and goes waits silently.
IProgressService.busyCursorWhile(...), on the other hand, does show the
reason why the task cannot start immediately, but is not as nice as a User
Job in reporting progress and providing flexibility to run in the
background. Ditto with IWorkspace.run(...).
How do I get the best of both worlds?
Thanks
|
|
|
Re: How to make a Job show the reason why it is blocked? [message #273194 is a reply to message #273160] |
Fri, 01 October 2004 09:01  |
Eclipse User |
|
|
|
I believe that the busyCursorWhile dialog just shows all the running
jobs and doesn't actually indicate which on is the blocking one.
Similarly, for user jobs, the dialog has a Details that shows all the
running jobs. The progress view also shows all the running jobs. I guess
the only difference with User jobs is that there is no visual clue as to
whether a running job is blocked by another job or is making progress.
You may want to log a feature request against Platform UI for this.
Michael
Wing Hong Ho wrote:
> A User Job is very nice in that it shows a Progress Dialog and gives the
> user the option to run it in the background. However, if the User Job
> cannot be scheduled immediately because of schedule rule conflicts, it
> doesn't put out a dialog that shows the reason and goes waits silently.
> IProgressService.busyCursorWhile(...), on the other hand, does show the
> reason why the task cannot start immediately, but is not as nice as a User
> Job in reporting progress and providing flexibility to run in the
> background. Ditto with IWorkspace.run(...).
>
> How do I get the best of both worlds?
>
> Thanks
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.15514 seconds