[rekonq] QTimer: ok but buggy

[Andrea Diamantini]

On Thursday 13 May 2010 23:34:53 megabigbug wrote:
> > I'm sure chrome uses a timer to show its suggestions, and I'm quite sure
> > also firefox does.
> > We can perhaps try with a shorter timer (100-150 ms).
> 
> I don't know about chrome but try firefox, konqueror or rekonq 0.3.
> The history list shows results instantly.
> We must fix bad painting performance, we must not apply workarounds.
> For google suggestions we will perhaps need qtimer, but not for history and
> bookmarks.
> 
> Lionel.
> _______________________________________________
> rekonq mailing list
> rekonq at kde.org
> https://mail.kde.org/mailman/listinfo/rekonq

firefox definitely uses a timer. A bit faster and a bit better implemented than
ours, but with the same logic: just fast type "ciao" and you'll see just 2 
suggestion lists: the first, based on "c" results, the second (final) based on 
"ciao" one.
I really don't consider this timer a workaround, anyway. Until we have 
suggestions based on "clear the previous list and show another one", it's 
necessary. And I really thinks it behaves well in almost all cases.

ps: 
google suggestions surely don't need timers, as they just have a not null 
retrieve & compute time. 

Regards,
-- 
Andrea Diamantini, adjam
GPG Fingerprint: 57DE 8E32 7D1A 0E16 AA52 59D8 84F9 3ECD DBF9 730F

rekonq project
WEB: http://rekonq.sourceforge.net
IRC: rekonq at freenode