Bug 252181 - Resizing images: "Start" button hidden after non-existent folder has been selected
Summary: Resizing images: "Start" button hidden after non-existent folder has been sel...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Bqm-Resize (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
: 245414 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-09-23 22:53 UTC by Christian Weiske
Modified: 2017-07-01 11:56 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.0.0
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 Christian Weiske 2010-09-23 22:53:45 UTC 
Version:           1.2.0 (using KDE 4.4.2) 
OS:                Linux

The scenario:
- Select some images in digikam
- Tools -> Resize images
- Destination folder is pre-filled, now I add "small/" to the end since I don't want to mix large and small, resized images
- I click "Start"
- I get an error message that the small folder does not exist. This is correct.
- I open the file dialog with the button on the right to the path box
- I create the folder manually and close the file dialog
- The "Start" button has vanished, and I have to close and re-open the resize dialog, re-selecting the small folder.

So the problem is that the Start button is away, and I have to re-open the dialog.
There are two solutions to the problem:
1. Ask me if I want to create the folder if it does not exist
2. Re-display the Start button if a new folder has been selected

Reproducible: Always




OS: Linux (x86_64) release 2.6.32-24-generic
Compiler: cc
Comment 1 caulier.gilles 2011-12-21 10:28:38 UTC 
Christian,

This file still valid using kipi-plugins 2.4 ?

Gilles Caulier
Comment 2 Jekyll Wu 2012-01-03 22:56:02 UTC 
*** Bug 245414 has been marked as a duplicate of this bug. ***
Comment 3 Jekyll Wu 2012-01-03 22:59:50 UTC 
The problem still exists when using kipi-plugins 2.4.1
Comment 4 caulier.gilles 2015-05-19 09:19:56 UTC 
*** Bug 338511 has been marked as a duplicate of this bug. ***
Comment 5 caulier.gilles 2015-05-19 09:30:30 UTC 
Christian,

This file still valid using kipi-plugins 4.10.0 ?

Gilles Caulier
Comment 6 caulier.gilles 2015-06-26 13:47:16 UTC 
New Kipi-plugins 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier
Comment 7 caulier.gilles 2015-07-04 10:10:47 UTC 
BatchProcessImage is not maintained since a while and is obsolete now. It will
be removed with 5.0.0.

Use digiKam BQM instead...