When I edit the database path manually, the cursor jumps to the end after entering the first character. Reproducible: Always Steps to Reproduce: 1. Go to: Settings - configure digikam - database 2. The database path be /home/photos 3. click after /home/ and enter: "horst/" Actual Results: The path now reads; /home/hPhotosorst/ Expected Results: The path should read: /home/horst/Photos
Widget used to edit Database path is KUrlRequester from KDElibs : https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/libs/widgets/common/databasewidget.cpp#L99 Problem is reproducible here. there is nothing special in digiKam code about Sound like a problem from KDELibs... Gilles Caulier
I cannot reproduce it using the KUrlRequester that are used in System Settings > Account Details > Paths. Does it also happen there? Can you please right-click the widget and check which "Completion mode" you use and try changing these?
No problems in systemsettings for me. Changing the text completion mode doesn't have an effect.
Gilles, could you re-check digikam code? Does the code connect to the textChanged() signal, and if yes, what does it do?
yes, it's connected to textChanged() to filter path entered by user : https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/libs/widgets/common/databasewidget.cpp#L236 Perhaps i need to use a timer here before to complete filtering and prevent slot cal for each characters enter in edit field ? Gilles
Git commit 646f4612f128dca8e32085447f93327164da7c0d by Gilles Caulier. Committed on 23/05/2014 at 12:10. Pushed by cgilles into branch 'master'. add timer to prevent bombarding signal over DB path edit field, which can corrupt path edited. FIXED-IN: 4.1.0 M +11 -3 libs/widgets/common/databasewidget.cpp M +9 -5 libs/widgets/common/databasewidget.h http://commits.kde.org/digikam/646f4612f128dca8e32085447f93327164da7c0d
This patch breakes config dialog when MySQL is chosen as DB backend. Please see: https://bugs.gentoo.org/show_bug.cgi?id=521992
To Johannes from comment #7 Problem still reproducible with last digiKam 4.8.0 ? Gilles Caulier
(In reply to Gilles Caulier from comment #8) > To Johannes from comment #7 > > Problem still reproducible with last digiKam 4.8.0 ? > > Gilles Caulier Was already fixed in 4.5.0 with: commit f0400ec7e518e753e0c4ccab4eb2b8b022f91767 Author: Gilles Caulier <caulier.gilles@gmail.com> Date: Tue Oct 28 15:58:55 2014 +0100 apply patch #89156 BUGS: 337737 FIXED-IN: 4.5.0