ah makes sense. maybe make that changeable via some preference? it makes a lot of sense on certain machines i guess?
thanks for the answer, reza On Mar 16, 10:44 am, Etienne Samson <[email protected]> wrote: > Yes, I was trying to reduce the amount of time spent on ranking > objects by preventing the search from happening if there were more > keystrokes coming (aka the user types "itunes", it prevents searching > "i", then "it", then "itu", then..., which uses CPU for almost nothing > more). I'm lowering the threshold from 0.333s to 0.150 for the next > version.
