At 9:24 AM +0800 9/26/06, Andy Dent wrote:
Lookup should be timer-based so it doesn't start doing things until there is a sufficient pause, say about quarter of a second. (You could do a really cool adaptive algorithm based on average speed of letters typed within words but it would be a lot more work.)
Why not just make it thread based and start a new lookup when more characters are typed? Spotlight's original immediate lookup and now time delayed lookups are both flawed, not because of when they start, but because the new lookup does not start immediately when new characters are typed and thus it's difficult / impossible to interrupt a prematurely started lookup.
If you do the lookup in a thread and kill any existing lookup and start a new one when more characters are typed you avoid Spotlight's problems.
Regards, Joe Huber _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
