When working simultaneously in different branches, closing of one leads to wrong error message: I want to shut down several branches of digikam independantly. If I click the close button of a window, I do _not_ get the presumably message "do you want to close/shutdown his process", but the (presumably) wrong error-message "do you want to close digikam". I assume, this to be a minor issue Reproducible: Always Steps to Reproduce: 1. just start digikam 2. begin (subsequently) several tasks 3. try to close one of these Actual Results: If doing so, I get the message "do you want to close digikam" instead of error message referring to the very task. This is misleading info; when working on longs tasks a writing tags, I cannot risk stopping, as I have to fear loosing hours of work...) Why? I assume this is either a logical mistake the very task would be closed but error-message is wrong, indicating the whole program digikam would be closed. Maybe the logical dependance between digikam and it tasks does not fit properly (> closing specific task, message general) Or, the logic behind is correct, only the message is misleading Expected Results: Very simple: It must be secured, that closing of a one window of a one task does affect _only_ _this_ very process. Neither misleading info (expressing to stop digikam as a program completely) nor other cross connection between digikam and its tasks
What do you mean by "working simultaneously in different branches" ? Gilles Caulier
Am 02.06.2012 10:20, schrieb Gilles Caulier: > https://bugs.kde.org/show_bug.cgi?id=301026 > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |caulier.gilles@gmail.com > > --- Comment #1 from Gilles Caulier <caulier.gilles@gmail.com> --- > What do you mean by "working simultaneously in different branches" ? > > Gilles Caulier > Running image editor PLUS writing all metadata in files PLUS batch manager, e.g. Axel
Axel, This entry still valid with digiKam 3.5.0 ? Gilles Caulier
Axel, What's about this file using last digiKam 4.2.0 ? Gilles Caulier
New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier
digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance.
This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier