Bug 375521

Summary: Progress bars waste useful space
Product: [Applications] digikam Reporter: bcr
Component: ProgressManager-UsabilityAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: caulier.gilles, freisim93
Priority: NOR    
Version: 5.4.0   
Target Milestone: ---   
Platform: Compiled Sources   
OS: macOS   
Latest Commit: Version Fixed In:
Attachments: Digikam progress bar screenshot, normal & enlarged

Description bcr 2017-01-24 20:36:18 UTC
All the current progress bars don’t offer a lot of value to justify themselves when shown
in larger form. Its ok to show % complete in the permanent one at the bottom of the window
but the larger popup ones represent wasted opportunities.

Additional items that could be shown in the same space:

* current file path   (very useful - confirms to user if operating on expected album/collection)
* items remaining
* estimated time remaining

Instead of this vacant thing:

 [       			15%        		  ]

...provide this instead:

 [  2015/05/14/Paris/eiffel.png        15%        4.5 min ]

If the file paths are too long to fit then trim from the right, showing the current folder
is more useful than the actual file:

[  2015/05/14/Pa…   15%   4.5 min ]
Comment 1 Simon 2017-01-24 20:37:48 UTC

*** This bug has been marked as a duplicate of bug 375519 ***
Comment 2 Christoph Feck 2017-01-24 23:35:19 UTC
Same bug from same reporter is not a duplicate, but invalid.
Comment 3 caulier.gilles 2019-12-29 04:52:42 UTC
Not reproducible with 7.0.0 beta 1.
Comment 4 bcr 2022-06-24 20:13:41 UTC
Created attachment 150131 [details]
Digikam progress bar screenshot, normal & enlarged

The enlarged view of the progress bar doesn't add any real value.  It should be overlaid with additional status info to assure the user that the job performing the right task on the right targets.
Comment 5 bcr 2022-06-24 20:16:58 UTC
Whoops, close this one if I reopened the duplicate - sorry
Comment 6 caulier.gilles 2022-07-07 07:05:08 UTC

*** This bug has been marked as a duplicate of bug 375519 ***