Bug 239924

Summary: okular should search after confirming the end of the word
Product: [Applications] okular Reporter: Yakup Turgut <y_turgut>
Component: generalAssignee: Okular developers <okular-devel>
Status: RESOLVED INTENTIONAL    
Severity: normal    
Priority: NOR    
Version: 0.9.5   
Target Milestone: ---   
Platform: PiSi Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Yakup Turgut 2010-05-28 22:32:14 UTC 
Version:           0.9.5 (using KDE 4.3.5) 
OS:                Linux

The default search behaviour of okular is to invoke search functionality after each key pressed however, this causes many problems i.e. performance while search in a long document. I thinks it is more convenient to search the word when users hits the Enter/Return. For example I will search for "okular" in a very long document, I start to write it to search box, it searches for 'o', then 'ok' etc until I finish writing and assume that I write it wrong in the first try i.e "olul" and notice it before finishing, If okular had waited, it would have not search for the wrong word which is totally time and source consuming.

Reproducible: Always

Steps to Reproduce:
hit ctrl+f then write a word to search box

Actual Results:  
it immediately starts to search the word

Expected Results:  
it should wait until word is finished, which is indicated by "Enter/Return"
Comment 1 Yakup Turgut 2010-06-05 14:49:00 UTC 
anyone there?
Comment 2 Albert Astals Cid 2010-06-06 12:37:21 UTC 
Yes, it is not going to happen, Okular gives you 300 ms to type another key, before starting a seach, this is a feature people use and love, so it's not going to be changed, sorry.
Comment 3 Yakup Turgut 2010-06-06 15:32:19 UTC 
I didn't see anyone who loves this feature, in fact many people I know hates this. Whatever. I think, rather than leaving this feature as it is, you should give users freedom to choose. People use this feature whether they love or hate, because they have to if they want to use okular and I think this is not nice. 

"The chief difference from other interface design philosophies is that user-centered design tries to optimize the user interface around how people can, want, or need to work, rather than forcing the users to change how they work to accommodate the software developers' approach." [1]

[1] http://en.wikipedia.org/wiki/User-centered_design
http://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration
http://en.wikipedia.org/wiki/Requirements_analysis