Toad World® Forums

can’t use F3 to search next appearance of the string


#1

Maybe this has already been reported. Wowever twice it better then ones.:slight_smile:

It’s from Alex:
Hi,

if you are searching in Nav 6.2.1.1521 a string in the Package editor you get a form to put in the search string. After closing the form you can’t use F3 to search next appearance of the string. This is because the editor window has no focus. You have to click into the editor window to give back the focus to use F3.

Best regards

Alex
(and Andre)


#2

Hi guys,

How did he close the Find window. I tried and the code editor gains focus right away. I didn’t have to click on it before using F3.

Gwen


#3

Hi Gwen,
regarding to your question Alex told me:
I close my find window with the escape key.

Regards
Andre


#4

I still could not reproduce. Could you please post a screenshot of the Find window before closing it?

Message was edited by: Gwen


#5

Hi Gwen,
it’s realy not that hard :slight_smile:

Alex took more care now to support you somehow:
Ok. Step by Step.
Go to a Package. Open the body.
Use F3 to open the Find dialog:
-> see pic001.jpg

  1. Press the Find button. The next appearance of the search text is marked.
    -> see pic002.jpg

  2. Now push the ESC key. The Find dialog disappeare appearance of the searched text are marked.
    -> see pic003.jpg

  3. Now push the F3 key. Nothing is happen. No more It is important that you not change the window in this constellation because to the Nav gets the focus back if you return.

  4. If you now click somewhere in the editor and push F3 the next appearance of the search text is marked.

Regards
Andre
pic001.jpeg


#6

Hi Gwen,
it’s realy not that hard :slight_smile:

Alex took more care now to support you somehow:
Ok. Step by Step.
Go to a Package. Open the body.
Use F3 to open the Find dialog:
-> see pic001.jpg

  1. Press the Find button. The next appearance of the search text is marked.
    -> see pic002.jpg

  2. Now push the ESC key. The Find dialog disappeare appearance of the searched text are marked.
    -> see pic003.jpg

  3. Now push the F3 key. Nothing is happen. No more It is important that you not change the window in this constellation because to the Nav gets the focus back if you return.

  4. If you now click somewhere in the editor and push F3 the next appearance of the search text is marked.

Regards
Andre
pic003.jpeg


#7

Hi Gwen,
it’s realy not that hard :slight_smile:

Alex took more care now to support you somehow:
Ok. Step by Step.
Go to a Package. Open the body.
Use F3 to open the Find dialog:
-> see pic001.jpg

  1. Press the Find button. The next appearance of the search text is marked.
    -> see pic002.jpg

  2. Now push the ESC key. The Find dialog disappeare appearance of the searched text are marked.
    -> see pic003.jpg

  3. Now push the F3 key. Nothing is happen. No more It is important that you not change the window in this constellation because to the Nav gets the focus back if you return.

  4. If you now click somewhere in the editor and push F3 the next appearance of the search text is marked.

Regards
Andre
pic002.jpeg


#8

These were what I did as well. I tried again but could not reproduce still.


#9

Hi Gwen,
we just found that it seems to be a windows 7 specific problem.
(I’m sorry, we should have checked this earlier.)

However, Alex told me this was not an issue in 6.2.0.
I hope it helps.

Regards
Andre


#10

I tested with Windows7 today but couldn’t reproduce either. Is that an English environment that you were using?


#11

Hi Gwen,

Im (Alex) using an German environment (MSWin7).
The interesting point is that is works in Version 6.2. Can you tell me witch DLL (Version etc.) has changed?
Maybe I can check some differences this way.

Best Regards
Andre


#12

Hi Gwen,
Please consider this from Alex - since he immolate big amount of time to find it out. Regards Andre

Here it is:
Hi Gwen,
I was able to reproduce the error with no focus after F3. The problem lays in the registry.
In the registry are three main entries for SQL-Nav:
a.) SQL Navigator 6.2.1
b.) SQL Navigator 6.2.1 Shortcuts
c.) SQL Navigator 6.2.1_BAK
I deleted the key SQL Navigator 6.2.1 started the Navigator and the problem disappeared. After this I imported the former registry entries and the bug comes again. I tried to delete a couple of entries, but without any success. My version of the Navigator was a upgrade from 6.2.0, so I think that maybe the upgrade is the reason for the corrupted registry entries. By the way, I am not the only one who has this bug. Another college has the same Problem after leaving the search form.
I send you my registry trees for both the fine working version and the version where the bug is coming up in a ZIP file:
Maybe you are able to reproduce the bug by using SQLNav6.2.1.fine working.reg. So it is possible to check what the reason for the Bug is.
Best regards
Alex
TEST.ZIP (39.8 KB)


#13

Hi Andre and Alex,

Thanks for spending so much time on this case. I finally figure out the underlying cause after checking the registry that you provided.

Not sure if you guys are aware of this bug but we used to have this issue where every time you open Task Manager this window drifts down and after a while becomes invisible. It looks like when you escape the Find window it moves the focus to this Task Manager and thats why pressing F3 doesn’t work. The issue with the floating window has been fixed so it won’t happen again but you still need to change the registry keys to make it visible. After that either close this window or dock it somewhere.
The keys you need to change are:
HKEY_CURRENT_USER\Software\Quest Software\SQL Navigator 6.2.1\Docking Windows\Layout0\13\FloatLeft
HKEY_CURRENT_USER\Software\Quest Software\SQL Navigator 6.2.1\Docking Windows\Layout0\13\FloatTop
Please change their values to 1.

Hope this helps,
Gwen