Summary: | File renaming in the queue settings don't manage tokens [date] and [cam] | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Philippe <pmiossec> |
Component: | AdvancedRename-BatchQueueManager | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | tschenser |
Priority: | NOR | ||
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.1.0 | |
Sentry Crash Report: |
Description
Philippe
2009-11-30 23:45:00 UTC
Date and camera token have been fixed in digikam-1.0.0-rc: http://www.flickr.com/photos/26732399@N05/4148688014/in/set-72157622697399159/ Also bei "Renaming Images" I guess you are talking about the KIPI-plugin (Tools->Rename Images)? The rename tool from BQM can also be found in the AlbumUI and CameraUI. The KIPI-Plugin "Rename Images" will not be loaded in digiKam-1.0.0-rc and higher, since it is replaced. Take a look at: http://www.digikam.org/drupal/node/485 and http://www.digikam.org/drupal/node/487 Cosmocat, does this solve your problems? Andi The new rename tool can be found in the toolbar ("Rename") as well as by pressing "F2". In earlier digiKam versions, F2 only renamed a single file, but now it can batch rename. It's in the Batch Queue Manager that I had the problem because in I have the beta 6 version in the fedora and in the "Renaming Images" menu item, I have the old renaming window. But if you say that it's fixed in the release candidate, I hope I could test it soon (when it will be packaged by the fedora team). I just submit the bug report because I couldn't find a similar one (and I couldn't test the RC for the moment). Thanks a lot... You can use it already (since beta5), just click the normal "Rename" action ;-) This one is also fixed, I think. Can anybody confirm? Yes I fixed this... if nobody broke it again... :-) I will close the report. Unit test ;) The unit test is working, this here would be an integration test... which we don't have... :-) We can misuse the unit tests for this as well ;) Hmmm not a fan of this... unit tests should not relay / depend on other classes... well anyway this bug is fixed :-) |