Community
Participate
Working Groups
There are cases like bug #252906 where the user has indicated "always run in background" and have initiated work that can take some time. Although the user can see the progress in the progress dialog embedded in the bottom right trim, it feels like we could do a little better a job of giving them feedback that a job has started. I'm not suggesting that the progress dialog itself be more eye-catching, just that the initiation of a job there should be. I think the problem in the case of #252906 is that a menu is picked at the top of the workbench, and progress happens in a small bit of trim at the bottom. It'd be interesting to see some kind of subtle animation technique which would draw the user's eye from the menu to the progress, or maybe better, a little animation flash in the progress when the job starts.
I like the animation flash idea. Something akin to the windows task bar item that flashes when something has happened there. Whatever the feedback is, it should only occur when job.isUser() is true.
Thinking about it a bit more...it might be worthwhile to have API that clients can call to "flash" a job in the progress bar. For example, consider a command handler that starts a job. We've said that some animation would help show the user that something was going on in the case where progress is in the background. Now suppose this job is still running, and the command handler is executed again before the first job is finished. In this case, the handler would probably want to "flash" the job as a way of telling the user "hey, I'm already working on this..."
Yes good use case.
I like the idea but we'd have to be careful not to over use it; the reason the person chose 'Run in background' at all was to get the UI out of their view. Having it flashing overly often (for some value of 'overly'...;-) would quickly get annoying I think. However, the 'already on it' scenario is a good use case where feedback may be warranted.
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.
