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 timeout, you still face the same problem. All it takes is a slow typist. You could implement a longer timeout yourself inside the scope. When you get the run() call, wait a while before actually firing the request; if you get a cancel(), while that timer is still active, don't send the request. (Don't add any delay to search(); doing so will cause the request to time out for the shell.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1394455 Title: 100ms timeout for query submission too brief Status in unity-scopes-api package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: There is currently a 100 ms timeout between keypresses and query submission. This is rather short and ends up submitting many queries while the user is still typing a delay of ~300 ms would eliminate many of these submissions while still being barely noticeable. See this thread for further discussion: https://lists.launchpad.net /ubuntu-phone/msg10361.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1394455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
