Version: 1.0 (using KDE KDE 3.4.3) Adept starts to filter the search results after each character the user types in. If the repositories which are being used are extensive, this will make the keyword writing a bit painfull. It would be nice if Adept only started to search after the user presses a "search" button or presses the enter key.
This is not the case, there is a (small) timeout between typing and filter kicks in. This should be probably extended a bit and enter used to fire the filter as well though. Would that be ok? Current timeout 400ms, maybe one second or something like that would be more suitable.
IMNSHO I believe that extending the timeout doesn't much sense, at least compared to the "search button/enter key" method. If the timeout limit is small then it gets in the way of typing, which was the reason for this whishlist entry. If the timeout limit is large, then the user will have to wait for it to work, which will make it spend time waiting for something that could come with a push of a button or a key press. But that is only regarding my personal taste. I find the "search button" method a whole lot better and the "automatic search" method a bit annoying and intrusive. On the other hand, it would be nice to have both options available if the auto-search functionality could be enabled/disabled somewhere.
a) it's easy to hit enter before the timeout if you are impatient b) a pushbutton would be needed to make it obvious you need to do something before filtering starts -- moving your hand from keyboard to mouse and hitting the button will almost surely take more than the second -- so the timeout saves time when user doesn't know about hitting enter c) pushbutton would cause clutter in the interface d) if you are slow typist, you will trigger an extra search -- which won't change your ability to finish the query in any way (i just verified this, the running search does not affect the lineedit in any way) and wait for the search to finish again e) if the search takes too long, the proper solution is to optimize the search (not completely easy) -- if you think that is the case, maybe file a bug about that f) adding an option for this does not make any sense
I was making a wishlist item, but it seems this one is telling it. I really would have the option (configurable) to make it possible to filter on demand, not on the fly. I agree with the OP. Cheers, Jeroen