Searching the collection takes an incredible length of time for collections of more than a couple thousand items. Since a complete redesign of item display is a lot of work, here are a couple of suggestions aiming to be quick patches. 1) Restrict search to substrings from the start of each word. In other words, don't search all n-grams, just those whose first character is the first character of a word. e.g.: "ring" would match "sensate's RING" but not "jarRING block" This would vastly reduce the search space. 2) Wait until no characters have been typed for N tenths of a second before performing the search. (Ideally an ongoing search would be canceled and replaced when new text was entered, but that's probably not feasible.) 3) I have no idea if the code does this, but it's always good to check that the computer is plugged in before debugging further: Don't individually re-evaluate each item according to the search criteria. If one item of a particular type doesn't match, none of the rest do.
Or as someone suggested, simply add a Search-button so it wouldn't automatically search while you're typing.
I just want to be able to sort by more than one column at a time, for example, Order by Token costs and then by Rarity is what I would use the most.
And while they are at it maybe optimize collections? Have an option to "hide all" collections so it doesn't load every time you go into a level or the Keep to check your current build or a store to check if it is selling something...
Oh okay. Yeah optimizing searching in the Wiki would be awesome, especially if you could optimize it by using filters like for expansion content! :-P *cough* http://forums.cardhunter.com/threads/suggestion-wiki-search-by-expansion-filter.5810/ *cough*
I'm adding a 0.5 second delay to the search after a key is pressed. It helps. Once I release, I'd appreciate thoughts on the delay length. It won't help if you are a slow typist, but it gets annoying if it's too long.
I have found in the past that 0.6 seconds is pretty nice. It's hard to notice up to that point. The other thing to consider is if client side caching is viable as search client side should be very quick comparatively - since the entire collection gets loaded when you enter the keep that seems like the data is there.
Will that same delay work for deleting text too? The most noticeable problem for me is several seconds of unresponsiveness when deleting a search term - it seems to take longer than typing the next one.
It's usually much faster to exit and return than to delete the letters one . . . . . . by . . . . . . . one. This can be tricky during an adventure, though.
I'm guessing the delay will work for deletion too, but in the meanwhile... use shift and the back arrow to highlight the whole word and press delete to delete it all at once, this is much faster!
