summaryrefslogtreecommitdiff
path: root/src/urlbar/urlsuggester.cpp
diff options
context:
space:
mode:
authorAndrea Diamantini <adjam7@gmail.com>2012-11-15 22:46:05 +0100
committerAndrea Diamantini <adjam7@gmail.com>2012-12-10 02:48:06 +0100
commit48645d6b81853f750c30ab9ed9af36163066969a (patch)
treeccd36d1dd6b1797c25681438eaa919f51a7e9c39 /src/urlbar/urlsuggester.cpp
parentopen target _blank link in new focused tabs, following chrom* & firefox (diff)
downloadrekonq-48645d6b81853f750c30ab9ed9af36163066969a.tar.xz
Clean up url suggestions, step 2
Do NOT qsort history results letting urlbar being A LOT more responsive. Can we live without (q)sort results??
Diffstat (limited to 'src/urlbar/urlsuggester.cpp')
-rw-r--r--src/urlbar/urlsuggester.cpp5
1 files changed, 4 insertions, 1 deletions
diff --git a/src/urlbar/urlsuggester.cpp b/src/urlbar/urlsuggester.cpp
index bc0ad280..6b9ccb13 100644
--- a/src/urlbar/urlsuggester.cpp
+++ b/src/urlbar/urlsuggester.cpp
@@ -326,7 +326,10 @@ void UrlSuggester::computeWebSearches()
void UrlSuggester::computeHistory()
{
QList<HistoryItem> found = HistoryManager::self()->find(_typedString);
- qSort(found.begin(), found.end(), isHistoryItemRelevant);
+
+ // FIXME: profiling computeHistory, this seems too much expensive (around 1 second for)
+ // Can we live without (q)sort results???
+ // qSort(found.begin(), found.end(), isHistoryItemRelevant);
Q_FOREACH(const HistoryItem & i, found)
{