1. Player opens a window with a search-field 2. Player types the first letter like 'a'. All list-objects with 'a' in the title are searched. Searching with one letter is very slow and there is no need to. One letter like 'a' won't say much about the content the player tried to search. Starting search at minimum with 3 letters would be great and saves a lot of performance. There's a bug in the search, too. While typing the first letter and there are too many things for search with no high-end-server, the letter is doubled. Repeatable behaviour, current version. You type in 'U' for searching 'Upgrade' and 'UU' is inserted. If you type to fast, other letters are doubled, too like 'UUpgradee'. Second I would insert a delay of at minimum 250ms for search, no instant. It would save hell-o-hylotl performance. Cause when you type 'Upgrade' the search searches 'U', 'Up', 'Upg', 'Upgr', 'Upgra', 'Upgrad' and 'Upgrade'.
This made me scratch my head over and over again... Do you only search for things using one letter? I can see the appeal but i am sorry if this upsets you with my understanding of this.
I agree, there needs to be a delay before it starts to actually search the string of letters you've typed in the search bar. But my biggest gripe is that the initial focus is on the dang search in the first place when I access a crafting bench or another object with a search function. It should never, ever be that way. Make the player click it, it's been very annoying. I could go on and on..
hey At the moment the search searches automatically every letter you type in starting from the first letter. If you type 'Upgrade' the search searches automatically after every letter typed in: 'U', 'Up', 'Upg', 'Upgr', 'Upgra', 'Upgrad' and 'Upgrade'. So there are six search requests till you typed in the word you're searching and mostly you only needed the last one. And the first searches are very performance-lacking. An 'U' will find more entries, many absurd, while an 'Upg' or 'Upgrade' will be a good search. Yes, agreed: no required search button. A delay would be the best practice. Optional: The focus-behaviour could be configurable for users (checkbox). If they wish, then search-fields are focused automatically while being available. Default-behaviour like I would like it would be: if search-input field is available in opened window then focus it automatically. If search-field has focus and user clicked somewhere, then focus is lost (prevent interception of key-binding, because user may type "i" for inventory to look for something while there is a search-input somewhere).
