The 23 october 2006 build is out.

[skirby]

I have found a little problem with the Find dialog box.
...

should be corrected in the next nightly build

The problem still persists in the 10/24/2006 build   

[tiwag]

I have found a little problem with the Find dialog box.
...

should be corrected in the next nightly build

The problem still persists in the 10/24/2006 build   

there are a lot of checkboxes, which influence the behavior,
please post a screenshot and describe again exactly what you do
in order to produce this bug.
thanks,

[skirby]

OK, here is the way to reproduce the problem (with screenshots)

- Create a new file an paste this piece of code :
aaa TestFind bbb
ccc TestFind ddd

Now select the text TestFind on the first line

Press Ctrl+F


Press Enter key to find the text => you should find TestFind on the second line

See screenShot


Now select the text Test on the fisrt line


Press Ctrl+F


and press Enter => you stay on the first line

Press F3 to go to the next occurence => Nothing happen

Can you reproduce it?

If yes, do you want me to add this problem on BerliOS?

For information, I am using C::B on windows 2000 sp4

Thanks and have a nice day.

[tiwag]

OK, here is the way to reproduce the problem (with screenshots)
...

thanks for the good report !!!

Can you reproduce it?

yes, the problem is, that Search scope changes to "selected" text instead of staying on "Global"
that's the reason, why F3 does "nothing visible"
but it works, if you change to "Global Scope" before pressing Enter 

If yes, do you want me to add this problem on BerliOS?

thanks, not necessary, i'll look at this problem soon ...

brgds,

[Pecan]

OK, here is the way to reproduce the problem (with screenshots)

- Create a new file an paste this piece of code :
aaa TestFind bbb
ccc TestFind ddd

Now select the text TestFind on the first line
Press Ctrl+F
Press Enter key to find the text => you should find TestFind on the second line

Xp svn3139
Mine ends on the first line.

Now select the text Test on the fisrt line
Press Ctrl+F
and press Enter => you stay on the first line

Yep, stays on the first line

Press F3 to go to the next occurence => Nothing happen

Nope, goes to the second line

Can you reproduce it?

I can't reproduce this problem on:
Version 1.0 revision 3139 (2006-10-24 08:52:45)   gcc 3.4.4 Windows/unicode

[tiwag]

it is actually not a bug - it's a feature 

we have implemented, that Search Scope automatically changes to "Scope: selected text" if the actually selected text doesn't match the last search criterion.
This doesn't harm if you always use F3 / Shift-F3 for searching the next occurrence,
but interferes as described above when you go through the FindDlg.
it could be changed maybe in the way, that the Scope doesn't automatically changes to "Scope: selected text"
if the slection doesn't go over several lines (which is normally when you want to find in Selected text) ...

But really i think it should stay as it is ...
if someone has problems, he might read in what state the checkboxes of the FindDlg are 

[killerbot]

another problem : have some selected text, and make sure your selection is done, in such a way that the focus in the editor is at the beginning of the selection. Search for something different then the selection and change the scope to global, ==> the search starts "AFTER" the previous selected text.

[tiwag]

another problem : have some selected text, and make sure your selection is done, in such a way that the focus in the editor is at the beginning of the selection. Search for something different then the selection and change the scope to global, ==> the search starts "AFTER" the previous selected text.

hi killerbot
this problem is selfmade 
see your commit 2609
brgds

[killerbot]

another problem : have some selected text, and make sure your selection is done, in such a way that the focus in the editor is at the beginning of the selection. Search for something different then the selection and change the scope to global, ==> the search starts "AFTER" the previous selected text.

hi killerbot
this problem is selfmade 
see your commit 2609
brgds

* Searching : several fixes/changes (NOTE : analog changes for replacing will also be done)
- search in selection (find next/previous) remain in the scope of that selection
- fixed warning (gcc 4.x) : due to dead(unreachable) code (made that code back alive)
- made some search functions private

I'll have a debugging session ahead of me ;-)

[severach]

Why not make an installer that accepts the nightly build packages? This opens the nightly builds to everyone and you only need to update it a few times a year.

[killerbot]

I'll have a debugging session ahead of me ;-)

done :-)

Problem

another problem : have some selected text, and make sure your selection is done, in such a way that the focus in the editor is at the beginning of the selection. Search for something different then the selection and change the scope to global, ==> the search starts "AFTER" the previous selected text.

is solved : revision 3164

another problem : have some selected text, and make sure your selection is done, in such a way that the focus in the editor is at the beginning of the selection. Search for something different then the selection and change the scope to global, ==> the search starts "AFTER" the previous selected text.

hi killerbot
this problem is selfmade 
see your commit 2609
brgds

No it's not, 2609 still is correct. The problem was there already before. The coordinates of a selection should not be used when the scope was changed back to global. That simple !!!

[gmiranda]

Why not make an installer that accepts the nightly build packages? This opens the nightly builds to everyone and you only need to update it a few times a year.

I've made two installers: one with MinGW and one without it. Then, I have an updater which upgrades the installed Code::Blocks to the nightly build that you've downloaded.

A user called yarocco offered hosting the setups, but I haven't heard from him/her in a while.