Version: 0.41 (using KDE KDE 3.1.4)
Installed from: SuSE RPMs
To rename a picture, I select it, then doubleclick on the name, and kooka will now let me enter the new name. Once I do this, the picture is immediately deselcted, and removed from the image view. 90 persent of the time, I now want to do something else with the picture, view it, rotate it, whatever. This means I have to reselect it, which means it has to be loaded again, possibly taking several seconds to load. it would be much better if the picture were not deselected in the first place after renaming, thus you can continue to work with it immediately. Plus, why waste the copy you allready have in memory at that time ? Not sure if this should be bug or wishlist, but it's kooka doing something that looks wrong, so I put it in bug for now.
Fixed in SVN version, commit 781253. Please check out and try this version (from branches/work/kooka-kde3) if possible.
SVN commit 784536 by marten:
Report more information for errors while scanning
Populate gallery subfolders when their parent is opened, bug 132699
Update gallery parent directory when an image is deleted, bug 70473
Don't deselect or unload image when renamed, bug 68532
ScanPackager::slAddImage() -> addImage(), it doesn't need to be a slot
Improve scan saving error reporting, move most of it to ImgSaver
Add "Properties" option for gallery images and folders
Accept any PNM file for SANE Debug testing
M +124 -179 kooka/imgsaver.cpp
M +7 -6 kooka/imgsaver.h
M +2 -0 kooka/kocrgocr.cpp
M +7 -0 kooka/kooka.cpp
M +1 -0 kooka/kooka.h
M +1 -0 kooka/kookaui.rc
M +13 -11 kooka/kookaview.cpp
M +87 -106 kooka/scanpackager.cpp
M +9 -6 kooka/scanpackager.h
M +1 -1 libkscan/kscancontrols.cpp
M +36 -41 libkscan/kscandevice.cpp
M +1 -1 libkscan/kscandevice.h
M +27 -0 libkscan/kscanoption.cpp
M +3 -0 libkscan/kscanoption.h
M +8 -3 libkscan/scanparams.cpp
WebSVN link: http://websvn.kde.org/?view=rev&revision=784536
Thank you for the bug report.
As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.
If this bug is no longer persisting or relevant please change the status to resolved.