Annoying problem with "find all" and edit step-by-step

[x3po]

Hello,

i have an annoying problem when using the "find all"-functionality.
Lets say i search for a string "test", and this string is like 5 times in my file. When i search with "find all", all 5 results are shown. That's nice so far.
When i click on the first result, the cursor jumps to that position. That's good. When i edit the string "test" in like "test1" or something, and i want to jump to the next result by clicking on it in the message pane, nothing happens. That's bad. I have to start another "find all"-command to get to the next results.

By clicking F3 i can still jump to the next result, but it would be great if the results in the message pane would stay clickable.

Regards.

[Karlis]

The problem is that when you change the text, the old results no more are valid, because the text has changed and all the positions are changed, this is why it does not work.

[x3po]

Hmm, that means, that Webuilder always "scans" those results shown for changes?
I think that's an odd behaviour, as in Homesite or Notepad++, the results stay in that state as at the moment when the search was done.
I think that it's possible, even in Dreamweaver or any other Editor, to click through the results and change something without loosing those results.
Regards.

[Karlis]

So what you are saying is that a simple solution would be to remove the "checking" of whether the found item is still at the old location?

[x3po]

Hey there,

ok, i investigated that issue a little more and noticed that notepad++ and homesite also f**k a little bit up when you replace the code of the search result with different content. but - the results stay clickable in homesite and n++, although the results don't get highlighted properly.

Maybe that would be enough for WeBuilder, if you're still able to click on the results and get forwarded to the line and position, that was valid when the search got started.

Got what i mean?

Best regards!

[Karlis]

I see.

[CaliforniaJerry]

I think that it's possible, even in Dreamweaver or any other Editor, to click through the results and change something without losing those results.

Just wanted to say I agree with x3po, that getting to the next line, even though the line numbers are off and the text isn't highlighted correctly, is better than not being clickable. Thanks.

[syrupcore]

why not just hit f3?

I realize you know you can do that but I'm curious what this solution *doesn't* do for you. it's all I ever need.

[CaliforniaJerry]

F3 performs a "Find Next", not a "Find All" which is what's important. It's still not fixed in WeBuilder 9.5.2.106.

I'd also like to add that it is unfortunate that in the text results column, the beginning of the line is cut off. I need to see the entire line to determine it's context and whether it is the code I need to modify. I can't do that with just a line "snippet". The results column should be expandable so you can view the entire line if it is long. In DreamWeaver 8, the search text is underlined in Red. That is very helpful.

Also, since the results are located in one document, you only need to indicate [current document], or perhaps [../end_of_path/file-name.php]. You can refer to DreamWeaver v8.0 for this behavior also.

I was going to check out the behavior, just now, of what happens when I perform a "Find In FIles", but the program locked up. I couldn't access my task bar, and had to terminate the process with Task Manager. (Windows XP SP-2, 2.5 GB RAM)

[Karlis]

This is not a bug, it is how it works in many software programs.

We have changed this, however. In version 2010 you will get to the position regardless of whether the file has changed. You will just get an background warning (a beep or message in status bar) that the file has changed.

[syrupcore]

still don't really get it. find next * n = find all, right? if (find next == 0), yer done.

[CaliforniaJerry]

Sorry, I was not implying that F3 should Find Next in the Find All results, although that might be interesting. I was simply responding to Will's (syrup's) prior post as to why F3 was not good enough. And as to why it doesn't "work" for me, I use the Find All In Files quite a bit. It is much more powerful than F3. It is also why I have posted a Feature Request for better handling of the Find ALL results. Better Results Display

[syrupcore]

ah. for sure, 'find in files' is a different beast.

[CaliforniaJerry]

When i click on the first result, the cursor jumps to that position. That's good. When i edit the string ... and i want to jump to the next result by clicking on it in the message pane, nothing happens. That's bad. I have to start another "find all"-command to get to the next results.

Found a partial work-around:
Start at the BOTTOM of the list of results links. You can edit that line, then procede UP the list.

[syrupcore]

Start at the BOTTOM of the list of results links. You can edit that line, then procede UP the list.

nice hack!