Just keep also in mind that the prototype is far from being perfect: if the communication / database / program is pretty slow, GDC's type ahead will buffer each keystroke and you may end with a 100% CPU time on the desktop and on the server too, as GDC has today no way to cancel the type ahead and the request.
I've been playing with a psuedo autocomplete just using dialogtouched (haven't got to using 2.30 yet). To really make that work I'd ideally like to be able to ignore the keystrokes until there has been a quarter or half second pause in typing - so input is not slowed up for users who are quick on the keyboard. I'd only fill my autocomplete data after the pause is sensed.
So, while you are working on this 'autocomplete' feature, can you have this in mind and (assuming the technology allows it) add a parameter to not execute any completion code until a pause (of a configurable time) in typing is sensed? Would be quite handy especially if the autocomplete code is hitting a large number of rows from the database as the first search will already be more refined if user has already typed 3 or 4 characters.
Cheers, Bryce Stenberg.
Sign in for full access
Help
