| Summary: | Don't init search till user press a buttom specifically for this task | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Rafael Linux User <rafael.linux.user> |
| Component: | Searches-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version: | 5.9.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 6.0.0 | |
| Sentry Crash Report: | |||
Is not really a big deal and often desired... Maik *** This bug has been marked as a duplicate of bug 221345 *** Git commit d77cf9bbbda0152a340e7b7977328a70aba863fb by Maik Qualmann. Committed on 06/07/2018 at 19:54. Pushed by mqualmann into branch 'master'. add autostart action to the right button context menu from the search edit field FIXED-IN: 6.0.0 M +2 -2 NEWS M +49 -2 core/utilities/searchwindow/searchtabheader.cpp M +1 -0 core/utilities/searchwindow/searchtabheader.h https://commits.kde.org/digikam/d77cf9bbbda0152a340e7b7977328a70aba863fb |
The search tab in the left side of Digikam, is very usefull. However, it has IMHO a big functionallity problem: The "autosearch". It begins to search entire database just when you open this tab ("New search" not "Advanced search"). This is slow for few elements database, but if you have thousand elements, Digikam stays insane time to show you the images. Even if you begin to type in the search form, it begins to search at each typed character, making impossible to control this search cause at each new character is beginning a new query (in my case, to internal mysql). This feature is the most interesting but as is implemented, is unusable for large databases. Please, could you implement at least an option en Digikam preferences to let the user enable/disable "auto search" to avoid that automatically begins the searching? Thank you