[rekonq] QTimer: ok but buggy

[andrea diamantini]

Not sure about this. Timer helps rekonq in not "flash results" in fast
typing, just that.
If you type a bit slowly you have everytime all the results.
If you fast type something and you don't want to wait just 0.20 sec to see
results and to decide what suggestion select, what can we do about this?
People that can type fast usually types 180-200 (max 240, I can ) chars per
minute. This means from 3-4 types per second, so 0.25 sec per type.


2010/5/13 megabigbug <megabigbug at yahoo.fr>

> Le jeudi 13 mai 2010 14:25:22, Cédric Bellegarde a écrit :
> > Hello,
> >
> > after using rekonq with qtimer in place, there is one bug :(
> >
> > First, i discuss with lionel about the timer, it's needed, even more if
> we
> > use google suggest in future...
> >
> > Current bug is that if you type too fast a valid host name: it do a
> google
> > search instead of going to host... QTimer block execution of
> > placeTypedDomaineNameOnTop()...
>
> it works here.


> > Don't know how to fix this :-/
> >
> > --
> > Cédric.
> > _______________________________________________
> > rekonq mailing list
> > rekonq at kde.org
> > https://mail.kde.org/mailman/listinfo/rekonq
>
> The qtimer allows to display the list only when the user stop typing.
>

it depends how much fast user types


> In my opinion the qtimer doesn't not solve real performance problems.
> History and bookmarks should be instantly displayed each time the user
> press a
> key. It is in all other browser. We must not fail to provide this feature.
>

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).


> _______________________________________________
> rekonq mailing list
> rekonq at kde.org
> https://mail.kde.org/mailman/listinfo/rekonq
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/rekonq/attachments/20100513/c22a7685/attachment.htm