When working with batch queue manager, one needs to determine to path, where the resulting pic ist safed after processing. for my opinion , this is not ergonomical at all. Reproducible: Always Steps to Reproduce: 1. run BQM 2. for every batch, you are asked for storage directory 3. rthis is time comnsuming and ineffective Expected Results: I would change the storage strategy: instead of asking storage path for every batch, I wish pics to be safed in the directory of the referring pic. Only in cases, one need to store resulting pics _at_ _different_ places, the existing menus should stay.
And why not to plan another idea : to have a default place to store BQM work. Look into Camera setup, we have a similar way to config a default download place which will always be used at download sessions. Why not to extend this feature to BQM ? Gilles Caulier
*** Bug 282674 has been marked as a duplicate of this bug. ***
The original subject of this file have been changed. There is a duplicate file about : bug #282674 Gilles Caulier
Am 21.12.2012 11:29, schrieb Gilles Caulier: > https://bugs.kde.org/show_bug.cgi?id=301378 > > --- Comment #1 from Gilles Caulier <caulier.gilles@gmail.com> --- > And why not to plan another idea : to have a default place to store BQM work. > > Look into Camera setup, we have a similar way to config a default download > place which will always be used at download sessions. Why not to extend this > feature to BQM ? > > Gilles Caulier > For me, this is not the idea: loading pics from camera, is step 1. There maybe days or week to the next shooting session. When I have some spare time, I do improving, selecting or sizing pics, completely independent from other tasks. My original idea refers to this situation: and I suggested, that changed pics should be at the _same_ place as the originals. Besides. what do you do, when you work with more than one camera? What, if a camera does not support a specific storing location as you? For me, this is a matter of workflow, efficience, and, so to say, professionality. Axel
Am 21.12.2012 13:02, schrieb Gilles Caulier: > https://bugs.kde.org/show_bug.cgi?id=301378 > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Summary|storage paths should store |Add a default place to BQM > |at the location of the |settings to store target > |referring pic, |files processed by BQM > |automatically | > > --- Comment #3 from Gilles Caulier <caulier.gilles@gmail.com> --- > The original subject of this file have been changed. There is a duplicate file > about : bug #282674 > > Gilles Caulier > thank you: ok!
Note : bug #282674 is fixed at 90% on my computer. I plan to commit code this week end before 3.0.0 RC release Gilles Caulier
What about this issue state?
Not yet implemented... Gilles Caulier
I just tested this issue, and on actual repository version 4.6.0 it works as expected when the "Use original Album" is enabled under target. Hence, from my point of view, this bug report can be closed.
Jan, I think the whish of this entry is to have a default and common place to store processed files by BQM, as it's already exist for Import tool to store downloaded files from camera. Look in Setup/Camera/Behavior section from config dialog and option "Use a default target album to download from camera" It's not to much difficult to implement this feature i think. Gilles Caulier
Ok, I will look for than in the future. First, I want to fix the bugs regarding the restoring of BQ tool parameters.
*** Bug 296192 has been marked as a duplicate of this bug. ***