The 16 June 2013 build (9158) is out.

[LETARTARE]

I found some possible improvements:

1- FILES WITHOUT TARGETS

   'CodeBlocks r9156'
      - 'sdk\nullptr.cpp'
      - 'wxsmith\debuggersettingspanel.wxs'
   'CC Test' : 'src\plugins\codecompletion\'
      - 'cctest\test.h'
   'wxSmith' : 'src\plugins\contrib\wxSmith\'
      - 'wxwidgets\defitems\wxsmediactrl.cpp'
      - 'wxwidgets\defitems\wxsmediactrl.h'
   'Tools Plus Plugin' : 'src\plugins\contrib\ToolsPlus\'
      - 'update.bat'

2- TO AVOID WARNING XGETTEXT :
   FILES CONTAINING _("") TO REPLACE _T("") OR wxT("")

   'CodeBlocks r9156'
      - 'src\scriptingsettingsdlg.cpp' : L128
   'wxWidgets - Contrib Items'  : 'src\plugins\contrib\wxContribItems\'
      - 'wxSpeedButton\wxSpeedButton.h' L73, L89, L90, L107
   'wxSmith'  : 'src\plugins\contrib\wxSmith\'
      - 'wxwidgets\defitems\wxsimagelist.cpp' L206
      - 'wxwidgets\properties\wxsimagelisteditordlg.cpp' L1213
   'wxSmith - Contrib Items' :   'src\plugins\contrib\wxSmithContribItems\'
      - 'wxled\wxsLcdWindow.cpp'  L33
      - 'wxled\wxsLedNumber.cpp'  L34
      - 'wxled\wxsLedPanel.cpp'  L48
      - 'wxspeedbutton\wxsSpeedButton.cpp'L80:
      - 'wxtreelist\wxsTreeListCtrl.cpp' L142, L150, L318, L410, L476
   'wxSmithAui - wxAUI' :'src\plugins\contrib\wxSmithAui\'
      - 'wxAuiManager\wxsAuiManager.cpp' L108, L116
   'FileManager Plugin'  : 'src\plugins\contrib\FileManager\'
      - 'directorymonitor.cpp' L518
   'ThreadSearch'  : 'src\plugins\contrib\ThreadSearch\'
      - 'ThreadSearch.cpp' L656, L660
      - 'ThreadSearchLoggerBase.cpp' L52

3- FILES CONTAINING wxT("blabla") TO REPLACE _("blabla")

   'src/plugins/compilergcc/compileroptionsdlg.cpp'
      L2851, L2875
   'src/plugins/contrib/BrowseTracker/ConfigPanel.cpp'  (from wxFormBuilder)
      L27, 39, 42, 50, 52, 61, 63, 72, 84, 86, 92
   'src/plugins/contrib/SpellChecker/ThesaurusDialog.cpp'
      L44, 53, 65
   'src/plugins/contrib/codesnippets/Search/SearchInPanel.cpp'
      L35, 37, 39
   'src/plugins/contrib/codesnippets/Search/ThreadSearch.cpp'
      L411, 448, 449, 459, 460, 604
   'src/plugins/contrib/codesnippets/Search/ThreadSearchConfPanel.cpp'
      L44..63, 69, 75, 81, 87, 124, 125, 303,
   'src/plugins/contrib/codesnippets/Search/ThreadSearchConfPanel.h'
      L47, 52
   'src/plugins/contrib/codesnippets/Search/ThreadSearchLoggerList.cpp'
      L150, 167, 249, 142, 158
   'src/plugins/contrib/codesnippets/Search/ThreadSearchView.cpp'
      L73, 76, 77, 80, 295, 296, 837, 838
   'src/plugins/contrib/codesnippets/codesnippets.cpp'
      L1816
   'src/plugins/contrib/codesnippets/codesnippetsapp.cpp'
      L431..434, 548..550, 576, 582
   'src/plugins/contrib/codesnippets/codesnippetstreectrl.cpp'
      L855, 1775...1777, 1868..1870
   'src/plugins/contrib/codesnippets/CodeSnippetsWindow.cpp'
      L970, 1480..1482, 1515..1540
   'src/plugins/contrib/codesnippets/editor/DragScrollCfg_H.cpp'
      L26....128
   'src/plugins/contrib/codesnippets/SettingsDlg.cpp'
      L58
   'src/plugins/contrib/codesnippets/SettingsDlgForm.cpp'
      L32....121
   'src/plugins/contrib/codesnippets/SnippetPropertyform.cpp'
      L54....86
   'src/plugins/contrib/codesnippets/SnippetPropertyform.h'
      L73
   'src/plugins/contrib/dragscroll/dragscrollcfg.cpp'
      L15....127
   'src/plugins/contrib/keybinder/cbkeybinder.cpp'
      L351, 518, 563, 624..628, 736
   'src/plugins/contrib/keybinder/keybinder.cpp'
      L1941....1987, 2002.....2072, 2768..2778
   'src/plugins/contrib/keybinder/keybinder.h'
      L1342, 1351

copy the attached file.

[oBFusCATed]

Please post patches at the project page in berlios.de.

http://wiki.codeblocks.org/index.php?title=Creating_a_patch_to_submit_to_BerliOS_%28Patch_Tracker%29

[Jenna]

Since svn9128 if that helps.

Does it mean that 9128 is bad and 9127 is good?
Or is 9128 the first revision where you recognized the issue ? If yes which was the last good one (if you still know) ?
Or is 9128 the last good revision you know and a later one is bad ?

For the build issue (prep.h etc.), I also see it when using the C::B workspace-file on linux.

I will look into it.

[MortenMacFly]

I found some possible improvements:

I saw that the attached file is not a patch. Can you try to provide a patch, please? Its very simple! just checkout the sources, then change the lines as needed and then issue the following command in the root folder of your svn-controlled working copy of C::B:
svn diff > translation_issues.patch
(Assuming that you have the svn command line tools installed, if not, please do so before and point to the svn executable.)

[MortenMacFly]

it remains highlighted until to enter semicolon at the end of your current line, or use the arrows to interrupt it.

What platform, btw? I cannot reproduce on Windows, at least. I've used exactly the code you have shown...?!

[LETARTARE]

@MortenMacFly
thank you.
yes indeed I know, but for extensions, I thought he had the agreement of the author.
The files without target, what to do ?

[MortenMacFly]

The files without target, what to do ?

What exactly do you mean by that?

If the file is not existent in SVN, do:
svn add the_file
before the svn diff command.

[Alpha]

Add -ansi to all projects that fail.

I am not on my computer right now, but attached is an easy commit for someone.

it remains highlighted until to enter semicolon at the end of your current line, or use the arrows to interrupt it.

What platform, btw? I cannot reproduce on Windows, at least. I've used exactly the code you have shown...?!

I have occasionally observed this under Linux.  It is most likely something to do with smart tab jump, but I have not yet had time to see if I can figure out what.

[Jenna]

Add -ansi to all projects that fail.

I am not on my computer right now, but attached is an easy commit for someone.

I just committed a similar patch to all linux project-files (wx2.8 and 2.9).
I hope it fixes the build issue not only for me.

it remains highlighted until to enter semicolon at the end of your current line, or use the arrows to interrupt it.

What platform, btw? I cannot reproduce on Windows, at least. I've used exactly the code you have shown...?!

I have occasionally observed this under Linux.  It is most likely something to do with smart tab jump, but I have not yet had time to see if I can figure out what.

The green highlight colour occurs immediately if "Brace completion" is on and I type the left parenthesis (round bracket, neither square nor curly bracket). It highlights the right parenthesis and if I type a doublequote, it also highlights the right quote and all characters I type between it and the right parenthesis.
To reproduce:

• "Brace completion" checked in the settings.
• In the editor type printf( followed by ".
• You get printf("|") (the pipe-symbol is the caret's place).
• The right quote and the right parenthesis are green highlighted.
• Type another " .
• Now you get printf(""|) .
• All characters you type now are also green highlighted until you type (e.g.) another quote or a right parenthesis

[ToApolytoXaos]

Since svn9128 if that helps.

Does it mean that 9128 is bad and 9127 is good?
Or is 9128 the first revision where you recognized the issue ? If yes which was the last good one (if you still know) ?
Or is 9128 the last good revision you know and a later one is bad ?

Yes, 9128 is the first revision where I have found out this issue by accident. I don't remember such issue before.

[ToApolytoXaos]

it remains highlighted until to enter semicolon at the end of your current line, or use the arrows to interrupt it.

What platform, btw? I cannot reproduce on Windows, at least. I've used exactly the code you have shown...?!

On Debian testing with latest updates MortenMacFly.

[ToApolytoXaos]

To reproduce:

• "Brace completion" checked in the settings.
• In the editor type printf( followed by ".
• You get printf("|") (the pipe-symbol is the caret's place).
• The right quote and the right parenthesis are green highlighted.
• Type another " .
• Now you get printf(""|) .
• All characters you type now are also green highlighted until you type (e.g.) another quote or a right parenthesis

Actually, to reproduce it, try to use printf() as you have shown on third point, but instead of typing another double quote, use your right arrow to move your cursor next to right quote, add a comma to add your variable parameter and see the green highlight persisting to continue.

NOTE: You can try the same with std::cout << ("") and as soon as you use right arrow and enter comma next to double quote, it does exactly the same.

[Jenna]

svn r9078 seems to be the first bad revision ("* SDK: major update to core component wxScintilla: Pumped underlying scintilla to v3.3.1").

[ToApolytoXaos]

OK, the svn9161 that I have currently compiled produces the same issue.

When you run the updates, can you please tell me which plugin or part of project should I compile within C::B, so I could save a bit of CPU cycles and unnecessary energy?

Another thing is that when I run C::B within terminal without & at its end, I can see how parser works and works pretty fast, actually faster than loading the IDE from "run" command and use it accordingly. Usually with the latter option, most of the times parser would hang and force me to reparse the entire project which is a bit of annoying.

Is there a reason for such behavior?

[ollydbg]

I found some possible improvements:

Thanks for the contribution, as some devs said before, we need patch files.

1- FILES WITHOUT TARGETS

   'CC Test' : 'src\plugins\codecompletion\'
      - 'cctest\test.h'

I think this is by design, E.g. some code snippet cause our Parser hang. To debug this kind of issue, we use a CCTest project, and you just simply copy the code snippet to "test.h", and let the CCTest app to parse it. Now, if "test.h" cause Parser hang issue, then we even can't open CCTest correctly.