Community

Search results: keyboard up/down arrow keys don't work

One way to reproduce the problem:

Windows 2000.
Textpad 5.2.0
Configure/Preferences/View
View Options/Dockable log windows
Search Results NOT checked.

Open any file and select <1st string>
Find In Files <1st string>
Search Results window appears
ESC // to close dialog box
Up/Down arrow keys work as expected,
i.e. they move the cursor up and down the rows of the search results.

Alt-tab back to file and select <2nd string>
Find In Files <2nd string>
Search Results window appears
ESC // to close dialog box
Cursor is on line between the 2 searches
Up/Down arrow keyboard keys won't move outside these 3 lines

1 Found <N> occurrence(s) in <M> file(s) // for <1st string>
2
3 Searching for: <2nd string>

Problem continues for any addtional searches after that.

Workaround #1:
Move to a line above line 1 or below line 3 using the mouse.
Up/Down arrow keys work as expected.

Workaround #2:
Alt-tab back to the file
Alt-tab back to the Search results
Up/Down arrow keys work as expected.

Workaround #3:
Problem does not occur if you always begin the search from the Search Results window.

P.S.

Textpad rules!
Have used it for many years.
Always recommend it to my friends.

First, I should say that I'm running 4.7.3, so maybe I shouldn't comment on issues that concern 5.X.X.

However, what has sparked my curiosity is your use of Alt+Tab to switch windows.

Try some other means of switching windows, say, Ctrl+F6 (and Ctrl+Shift+F6).

Of course I am assuming that Ctrl+F6 is implemented in 5.X.X as it is in 4.X.X.

Does the problem continue to occur?

By the way, double-clicking on a line number in the Search Results window should instantly take you to the associating line in the appropriate file.

Whoops. I meant to say ctrl-tab. Alt-tab takes you to other applications. Ctrl-tab takes you to other open documents.

The problem remains with ctrl-F6 (which is identical to ctrl-tab). It does not matter how you get back to a file to conduct the next search. The problem occurs when transitioning from a file to the Search Results window. The problem does not occur if that transition does not occur i.e. starting the search with the Search Results window on top.

I was running 4.7.3 until yesterday when I upgraded. It does not have this problem.

I just confirmed that the problem also occurs with Windows XP Home Edition Version 2002 with Service pack 2.

Can someone with 5.2 try to duplicate this problem so I know if I need to check myself into the funny farm?

Here's the simplified and corrected way to make it happen:

Configure/Preferences/View
View Options/Dockable log windows
Search Results NOT checked.

Open a file.
Search / Find In Files some text (or use shortcut ctrl-F5)
Search Results window appears.
Close the Find in Files dialog box
Ctrl-tab back to the file
Search / Find In Files some text again
Search Results window appears
Close the Find in Files dialog box
The Up/Down arrow keyboard keys won't move the cursor up or down.
Click anywhere with the mouse.
The Up/Down arrow keyboard keys work correctly.

tomlamson,

I followed your simplified and corrected procedure and could not reproduce your problem in 5.2.0 on Vista Home Premium SP1. I can try it in XP in a few days' time.

Andrew

I'm using TextPad 5.2 on XP SP2 with the Search Results window undocked. I get this intermittently. I don't know precisely what triggers it.

Thanks ben and ak.

ben, the problem only and always occurs if you start the search with the file as the top document. If you start with the search results as the top document it does not happen. Could that be the intermittant part?

I tried it again XP SP2 as well. I still can't reproduce your problem, sorry!

Andrew

I tried this using Textpad 5.2 and English Windows Vista Business with SP1. I managed to reproduce this problem on the first try and it happen every time i do the described steps. Once the cursor up was working fine, but not down. Maybe i did the test a bit different that time.....not sure. Anyway i can confirm that i have similar problem as tomlamson on my computer.

tomlamson wrote:the problem only and always occurs if you start the search with the file as the top document. If you start with the search results as the top document it does not happen. Could that be the intermittant part?

I think it might well be.