Community
Participate
Working Groups
When running test connection on a site it is interesting to see what it is actually doing. Now the information is flashing in the lower right corner. Suggest that the dialog has a details button, and that detailed progress is displayed as this is a helpful tool in figuring out what is wrong if things are slow.
I'm going to take the liberty of moving this bug to platform UI for comment. What is requested is the "details area" function of ProgressMonitorJobsDialog to be available in the foreground ProgressMonitorDialog. This seems reasonable given the IProgressMonitor API supports detail via subtasks. I don't see that the detail necessarily depends on running the code in a job.
Makes sense to me.
The details button is useful when there are more tasks running (in the case of ProgressMonitorJobsDialog, a number of jobs). But ProgressMonitorDialog, needs to show the details of only one task. Can't it be done with the names of the SubProgressMonitor (assuming all the subtasks are using a SubProgressMonitor)?
Created attachment 136646 [details] With subtask
I think clients can get this today using IProgressService@busyCursorWhile (which despite the name shows a dialog after enough time has elapsed).
There is of course also the problem that ProgressMonitorDialog lives in JFace where there is no awareness of jobs, etc. I suggest this should be WONTFIX, and if people want a dialog that shows jobs in the details area, use IProgressService.
It's not that we want to show jobs in this dialog, is that we could show details about the subtasks.
(In reply to comment #7) > It's not that we want to show jobs in this dialog, is that we could show > details about the subtasks. > The screenshot I've attached provides details about the SubTasks. Isn't that enough? If not, can you provide a mock up of what you are expecting in the details?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.