Version: unspecified (using KDE 4.5.0) OS: Linux btw. my Gwenview version is 2.5.0., but I cannot select this in Bugtracker, the max is 2.4 When selecting batchprocessing/resize, then selecting files from several different folders, then selecting overwrite all, the resulting files are all written into the first folder found, overwriting those that are in the folder but leaving all other folders untouched. Reproducible: Always Steps to Reproduce: Select files from several different Folders, select overwrite all. Actual Results: writes all the files in the first folder found and leaves all other folders untouched. Expected Results: overwrites every single file in all the folders since I selected "overwrite all"
It's not writing the files in the first folder found, it's writing the files in the target directory (there is a field that defaults to the directory of the first picture selected). That is indeed problematic for processing files in different folders since you can on ly set one directory target..
I'm just wondering if it's not more kipi-plugins related than gwenview related?
This may be, I filed this here because it said "Gwenview and KIPI-Plugin integration". I have not tried this with other software that uses the KIPI plugin. (offhand, I do not know any) On the matter of the directory, I would have assumed that once overwrite (or anything else, for that matter) is selected, the full path of the original file is transmitted to the conversion and used, for each file individually. Thus why i wrote the bugreport.
I guess the problem with the default target folder is on the gwenview side. When using kipi-plugins from kphotoalbum, the default target folder is always $HOME. As for the behavior of overwritting, I guess that is totally the job of kipi-plugins.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!