Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set the default 'Wait before searching' time to 0.00s #340

Closed
philostein opened this issue May 29, 2011 · 5 comments · Fixed by #782
Closed

Set the default 'Wait before searching' time to 0.00s #340

philostein opened this issue May 29, 2011 · 5 comments · Fixed by #782

Comments

@philostein
Copy link
Contributor

philostein commented May 29, 2011

Preferences>Preferences>Command>Wait before searching>0.00s

After trying Patrick's hint on twitter, QS got significantly faster for me. The default is 0.1s (according to Patrick).

I thought the time delay concerned searches appearing in the results list, not the actual search time.

I reckon this would benefit a lot of users if it's a viable change. (My Intel MacBook is 5 years old.)

@pjrobertson
Copy link
Member

pjrobertson commented May 29, 2011

I only came across this when dealing with the bug I tried to fix in this
pull: #325

Does anyone know why you would have this set to anything other than
instantly?
There seems to be nothing about it in the manual?

As per Phil's suggestion, we could remove this option all together, and then
remove the lines of code around QSSearchObjectView.m:885

It definitely made QS feel a lot 'snappier' for me.

On 30 May 2011 01:04, philostein <
reply@reply.github.com>wrote:

Preferences>Preferences>Command>Wait before searching>0.00s

After trying Patrick's hint on twitter, QS got significantly faster for me.
The default is 0.1s (according to Patrick).

I thought the time delay concerned searches appearing in the results list,
not the actual search time.

I reckon this would benefit a lot of users if it's a viable change.

Reply to this email directly or view it on GitHub:
#340

@skurfer
Copy link
Member

skurfer commented May 30, 2011

I’ve always assumed it was there for slower machines. That is, if it takes a while for results to come back, you might want it to wait until you’re done typing to start the search instead of cranking away on stuff you don’t want. Maybe this isn’t as much of an issue as it was in 2003. :)

@ghost ghost mentioned this issue Oct 31, 2011
@pjrobertson pjrobertson mentioned this issue Dec 2, 2011
@pjrobertson
Copy link
Member

pjrobertson commented Mar 30, 2012

With my machine being significantly slower (Since upgrading to Lion) I am actually seeing a requirement for this setting now.

I use a value of about 0.05s, which seems to help significantly with loading objects, so I suggest we change the QSDefaults value from 0.1s to 0.05s. I will issue a pull request soon if I hear no objections.

@skurfer
Copy link
Member

skurfer commented Mar 30, 2012

Sounds fine.

@pjrobertson
Copy link
Member

pjrobertson commented Apr 2, 2012

Time has been halved to 0.05s, this will be present for new users only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants