https://bugs.kde.org/show_bug.cgi?id=396559
--- Comment #6 from IWBR <iwannaber...@gmail.com> --- But isn´t there a way not to freeze the whole interface while scanning for new items? Bug #389652 is basically a consequence of this. Ideally, you should be able to use Digikam even if it´s scanning for new items. Just like you can browse albums just fine while it´s writing metadata changes to files. I don´t know exactly how it´s been implemented, but maybe giving a higher priority to user actions rather than the background new file scan, so when in conflict, the user has priority? Like pausing for a moment the scan of a file/folder and do what the user has requested in the interface, and then resume the scanning. Or, as a last resort, tell the user that the interface won't be available during the scan. Otherwise, at least in Ubuntu, it constantly throws "Force close" messages to the user, which is not elegant. -- You are receiving this mail because: You are watching all bug changes.
