Bug 302925 - Add optional warning when doing mass edit of properties
Summary: Add optional warning when doing mass edit of properties
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Tags-Rating (show other bugs)
Version: 2.8.0
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
: 456973 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-07-02 21:21 UTC by julien.t43+kde
Modified: 2022-07-21 07:59 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description julien.t43+kde 2012-07-02 21:21:04 UTC 
When doing my pictures sorting, I working mostly with keyboard (netbook one, so a bit small, maybe ...). one mistakes which happened to me a few times is: Ctrl+A, Ctrl+1, instead of only ctrl+1 => as a result, instead of rating one picture, I did for all the album.

To avoid that, an configureable and optional warning could help preventing you to directly edit more than 50/100 pictures/meta (can configure the number as wanted, 50 would probably be a good default)

Alternative way to repair would be an undo/versioning option (mostly for metadata)

Reproducible: Always
Comment 1 caulier.gilles 2012-07-02 21:23:42 UTC 
I recommend quickly to test 2.6.0 release where Progress Manager have been introduced with background pipelined operation about files. This behavior since 2.5.0 has changed...

Gilles Caulier
Comment 2 julien.t43+kde 2012-07-02 21:56:58 UTC 
As said before, I have some work to be done and after, I will update system and digikam. Hope this week. After will update my bugs
Comment 3 julien.t43+kde 2012-10-11 18:45:33 UTC 
still valid in 2.8.0 (kde 4.8.5, lubuntu 12.04 ppa). The progress manager only allows to stop the task. I don't see any way how it allows a warning or a revert of a unvolontary mass action.
Comment 4 Maik Qualmann 2022-07-21 07:59:08 UTC 
*** Bug 456973 has been marked as a duplicate of this bug. ***