yes, though if you find yourself having this problem, moving to a 2 step launch process:
- hit a key to stop search then hit a key to launch.
may solve the problem because it gives you just enough milliseconds to stop yourself from launching if you notice the results changing while you were pressing the stop search key (down arrow, escape, etc.)
actually i suppose maybe FARR could be made to address this problem slightly couldn't it..
if FARR updates the display, and you hit launch within some small time window of the update, FARR could detect that right?
and then check if the item you want to launch got moved down during the update.
if so, FARR could either adjust it's guess of what you REALLY wanted to launch
or.. stop searching, beep and let you know that your launch request was interrupted by a late breaking update of list and you should choose again.
kind of cool idea.
Example:
Result list shows:
1. notepad
2. wordpad
3. ideapad
you hit the 2 key to launch wordpad.
as you are moving to hit the 2 key, a new result sneaks in at location 2, so that new results are:
1. notepad
2. evilpad
3. wordpad
4. ideapad
normally farr would now launch item 2. but in this case it knows that previous item 2 got shifted down a mere 100 ms before you hit the 2 key.
so it guesses that you could not have seen and reacted to this new number 2 so quickly. therefore you PROBABLY meant to choose the PREVIOUS #2 (now #3), wordpad.
so it could just go ahead and launch wordpad.
OR it could simply stop searching, give you a little sound tone letting you know it didn't launch anything due to caution, and needs you to select what you want to launch again.
what do you think, is it a fun enough idea that it's worth implementing? it would be optional of course, with user-selectable time window interval for this behavior.
