Bug 167797 - KPDF Search exit behavior not consistent
Summary: KPDF Search exit behavior not consistent
Status: RESOLVED NOT A BUG
Alias: None
Product: kpdf
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Astals Cid
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-31 01:34 UTC by nino
Modified: 2008-07-31 21:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nino 2008-07-31 01:34:26 UTC
Version:           3.5.9 (using KDE 3.5.9)
Installed from:    Unspecified Linux
OS:                Linux

When using KPDF and searching for a word within the PDF there is a behavior that causes the CNTRL-F (find) or F3 (continue search) to stop working.

If I search for a word and it does not find that work, I can either "click" on the "ok" box that is present OR just hit "enter" to close the dialog box.  Either method (mouse or keyboard) closes the dialog box BUT subsequent commands are now affected...

Method 1 - "click" the "ok" button
This method will allow me to now hit "cntrl-f" and issue a new search

Method 2 - hitting the "enter" keypad
This method closes the dialog box also BUT now using "cntrl-f" no longer brings up a new search window nor can I hit F3 to continue the search.  Hitting "enter" breaks the ability of KPDF to recognize subsequent hotkey commands.  I "can" continue searching by going to the menus and pulling down "find" or "find again" but I don't believe this is the way it "should" work; at least, this hasn't been my experience with most GUIs.

Thanks in advance.
Comment 1 Albert Astals Cid 2008-07-31 20:32:26 UTC
Can't reproduce it, are you sure that's the problem?

Just to see if i'm doing what should fail
 * open pdf
 * ctrl+f
 * search for gdhsghdfghsfgsdfg
 * get message saying gdhsghdfghsfgsdfg was not found
 * Press enter on the keypad
 * ctrl+f
 * works
Comment 2 nino 2008-07-31 21:25:46 UTC
ok, my bad...(hangs head in shame)...

Yes, this occurs but I should have mentioned that it was occurring when Seamonkey  embedded KPDF inside the browser window.  Still not sure why but the behavior does NOT occur with KPDF running on its own but when it is running from a window/tab of Seamonkey.  Not sure if that is a concern of KDE or Mozilla.
Comment 3 Albert Astals Cid 2008-07-31 21:32:00 UTC
Sorry but if it works in all KDE embedded apps and does not work in seamonkey, i'll bet it's a seamonkey issue unless proven wrong.
Comment 4 nino 2008-07-31 21:53:16 UTC
no need to apologize to me - I'm not offended as I don't work for Mozilla ;-)
I haven't checked it with all KDE embedded apps.  Feel free to close this and if I find that it happens in a KDE app then I'll file another.