This was recently explored by Design team as part of various minor UI
improvements and based on that research, the delay was increased to
700ms, therefore closing this bug.
** Changed in: unity-scopes-shell (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: unity8 (Ubuntu)
is run() in query.cpp?
Say I add `sleep(2);` (exaggerated delay to see results, later to fine
tune) before `infoslist = client_.infos(query_string);` even though I
still see Dispatching search: is the Dispatching Search dialog part
of the system (the part that sets the type rate, that then sends
You can follow what's going on by dropping some trace into your scope.
Basically, your search() method instantiates the query, and the run()
method is called to send the query executing in a separate thread.
You are supposed to be quick in search(), just instantiating the query
instance and not
Hi, Is there any progress on this. I'm hitting a hard stop on making my
scope.
So the problem is - the scope makes several requests while typing - e.x.
typing Douglas Adams will result in a series of multiple requests
like:
Dispatching search: ug
Dispatching search: ugl
Dispatching search:
I'm not sure whether lengthening the timeout would help all that much
(although I agree that 100 ms seems unnecessarily short).
Are you responding to cancel() messages in the scope? (The shell sends a
cancel for each outstanding request before it fires the next one.)
But, even with a 300 ms
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-scopes-shell (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394455
Hmmm? How is Unity8 supposed to control this timeout?
We do nothing, all the logic i see is in src/Unity/scope.cpp from the
unity-scopes-shell that has m_typingTimer that is set to 300 msec.
** Also affects: unity-scopes-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
From memory, this used to be 100 ms and was raised to 300 ms not that
long ago? Maybe it's just that the scope tool isn't up to date yet?
Robert, are you sure that you are really seeing 100 ms, not 300 ms?
The only source for queries is the dash or the scope tool, so unity-
scopes-api is
Re-assigning to Unity8 because it controls the timeout.
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-scopes-api (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
