The 16 June 2013 build (9158) is out.

[oBFusCATed]

Can't reproduce both problems on Linux.

What happens if you use View -> Toolbars -> Fit toolbars or View -> Toolbars -> Optimize ?
What windows are you using?

[carra]

I'm now on Windows XP, I'll try it under Vista later.

Fit Toolbars and Optimize Toolbars seem to work reasonably well. There were a couple of times when a toolbar had a small part of it outside the window width, but I can't find a sure way to reproduce it. I wouldn't worry too much about that though.

None of these options seems to have any effect on undocked toolbars.

[oBFusCATed]

None of these options seems to have any effect on undocked toolbars.

This is good, because the fit/optiomize commands are only for docked toolbars:)

[carra]

Lol! I meant that after using them the undocked bars bugs kept happening just the same

[oBFusCATed]

Unfortunately someone running windows should try to see if he/she can reproduce it and then debug it.

[ToApolytoXaos]

Well sorry to say that, but not for me. Here it works as expected - at least on Windows.

I do have some patches concerning Scintilla applied though, but they they should not affect this functionality.
I can apply them for testing, but I am not sure if this is fine for all...?!

I will test it on windows also (hopefully this weekend), but it might be a gtk-issue, so it would probably be better to wait.

The issue does not occur on windows.
I will look into it, later.

Sorry, but I will disappoint you now. I am on Windows at work with svn-9138 and the issue remains the same.

[golgepapaz]

Sorry, but I will disappoint you now. I am on Windows at work with svn-9138 and the issue remains the same.

Ditto . It's pretty annoying...

[Jenna]

Ditto . It's pretty annoying...

If that is already annoying for you, I hope you will never come in touch with real problems in your life.

[ToApolytoXaos]

This is getting really interesting...the issue (with bracket-matching highlighting) remains the same on both Debian jessie and windows.

[Jenna]

The issue should be fixed in trunk (svn r9171).
The cause was an incorrect use of IndicatorClearRange in void cbStyledTextCtrl::HighlightRightBrace().

IndicatorClearRange takes a position as first and a length as second parameter, but a position was given for both.
If position + length is greater than the documents length the indicators will not be cleared.
This behaviour has changed with the revision of scintilla we use since our svn r9078.
Older scintilla has cleared the indicators anyway.

That's why it happened since this commit.

Can you please test and give feedback.

By the way one of the green indicators is okay and used by the so called SmartTabJump-feature.

[ToApolytoXaos]

Thank you jens. It seems the issue kind of got solved. Another issue exists now.

Take a look at the standard coding I use to produce the issue:
() << () << (). As soon as I start moving from far left to right and reach the first << my first pair of parentheses highlight its right one. As you move along, the same repeat itself.

   ()| << () << () << ()
-------^    /* this is the blinking cursor supposedly */

[Jenna]

Thank you jens. It seems the issue kind of got solved. Another issue exists now.

Take a look at the standard coding I use to produce the issue:
() << () << (). As soon as I start moving from far left to right and reach the first << my first pair of parentheses highlight its right one. As you move along, the same repeat itself.

   ()| << () << () << ()
-------^    /* this is the blinking cursor supposedly */

Is the highlight colour the normal colour used for matching parenthesis or the colour we had before (a little more "greener").

What happens if you hit the tab-key in this situation ?

If it jumps to he right, it's the so called SmartTabJumping (http://forums.next.codeblocks.org/index.php/topic,12406.msg84207.html#msg84207).

I don't know how it should behave exactly.
I think the "feature" itself and its highlight-colour should be configurable.

[zetab]

The combobox on Incremental Search toolbar looks strange, is this normal?

[scarphin]

Is there a way to disable compiler checking before loading? CB brings up a list of detected compilers dialog every time before starting. That didn't exist before.

Win7 x64, rev 9158

[oBFusCATed]

Something is broken. It should do it just once.