The 01 October 2013 build (9378) is out.

[killerbot]

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx2812_gcc471-TDM.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc471-TDM.7z
And the exception handler dll (for better crash reports) : http://prdownload.berlios.de/codeblocks/exchndl_gcc471-TDM.7z

The 01 October 2013 build is out.
 - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20131001_rev9378_win32.7z
 - Linux :
   none

Resolved Fixed:

• find-replace-dialog: fix shortcut (was used twice)
• debugger: Improve GetEditorWordAtCaret to work correctly for non-rectangle selections (thanks Huki)
• wxSmith-plugin: immediately show changed size (after adding first image) and image count in wxsimagelisteditordkg, disable del-, clear- and save-buttons if list is empty
• wxSmith-plugin (wxsimagelisteditordlg): expand image labels, so larger numbers get not cut off; add button to save a single bitmap instead of only sving the list as one large bitmap; many differences come from autogeneration of the source files with actual wxSmith
• SDK: introduce CodeBlocksThreadEvent which is thread safe to carry wxString cross threads, also remove the mutex in CClogger class, as we don't need them. see the discussion: http://forums.next.codeblocks.org/index.php/topic,18059.0.html
• manager: Don't translate the name of all cbEVT_XXX types (thanks gd_on)
• wxSmith-plugin: fix layout issue; only the top-sizer with the title of wxsImageTreeEditorDlg was shown
• wxPropgrid: correct handling of composite flags in wxFlagsProperty; backport of my patch for wxWidgets, see: http://trac.wxwidgets.org/changeset/74808
• wxSmith- and wxSmithContribItems-plugin: correct handling of composite-flags in codegeneration of wxsRichTextCtrl, wxsRichTextFormattingDialog, wxsRichTextStyleOrganiserDialog and wxsChart
• debugger: Fix a crash when the locals or func args are disabled during debugging session
• debugger: Refresh watches, when locals or func args are added during debugging sessoin
• ui: Remove the shortcut for hiding the editor tabs, because it causes too much complaints in the forum
• CC: handle macro definition correctly, distinguish between function like macro definition and variable like definition (thanks Huki)
• CC: correctly find the end of a c style comment (thanks Huki)
• CC: only skip after single equal sign, not double equals sign (thanks Huki)
• CC: when reading the parentheses, set the correct Tokenizer mode(tsReadRawExpression), also skip comments after the first '(' (thanks Huki)
• ThreadSearch-plugin: initially load search history in toolbar combobox
• ThreadSearch-plugin: really remove last item of toolbarcombo, if max-count is reached
• ThreadSearch-plugin: use right-click event instead of menu event to invoke context-menu of logger-tree, this avoids annoying pop up of the infopanes context menu after the tree contextmenu was closed (happened at least with wxGTK)
• ThreadSearch-plugin: do not skip delete-event, to avoid double invocation of it, fixes an assert and (sometimes) crash with wx2.9+ (at least with wxGTK)
• ThreadSearch-plugin: immediately return from loggert-tree click event, if the tree was cleared; avoid annoying pop up of "Failed to retrieve file path and line number" messagebox after leaving configuration dialog (happened at least on wxGTK)
• pumped wxPDFDoc to 0.9.4 (includes many changes related to wx29)
• pumped (wx)scintilla to v3.3.5
• pumped astyle lib to v2.0.4 final
• applied patch #3478: Add line breaking option to AStyle
• applied patch #3480: Fix menu entry for scripts are not updated
• ui: Allow the user to change the colours of the linenumbers and the margin in the editor
• info_window: Improve multi monitor support
• CC: reliable working of UngetToken() when macro expansion is involved, it set the undo index value correctly(thanks Huki)
• CC: avoid take backward step (UngetToken) twice in the Tokenizer class
• colours: Use the proper constant for start page's background, wxSYS_COLOUR_BACKGROUND returns the destop's colour on windows (related to r9361)
• colours: Use wxSYS_COLOUR_WINDOWTEXT colour instead of just black for the text colour

Regressions/Confirmed/Annoying/Common bugs:

[kingfox]

wondeful!

[carra]

That's a lot of fixes, congrats!!

[gd_on]

Hi,
the title of the post should be with svn number 9378, not 9295.

gd_on

[scarphin]

Does code completition take into account the 'using' statements? I'm guessing it doesn't because cc doesn't kick in when I type 'cout.' if I use 'using std::cout;' but it does kick in when I write 'using namespace std;' or 'std::cout.'. I just wonder if that's a bug or a limitation.

[oBFusCATed]

CC handles using directives very poorly, unfortunately.

[p2rkw]

How long c::b uses gtk3?

[oBFusCATed]

How long c::b uses gtk3?

Hm, you'll have to try again, because it is not clear what are you asking.

[rathapolk]

When I go to properties on a file and tick "Use custom command to build this file" in Advanced tab, it will automatically tick "File is read-only" in General tab. Is this an intended behavior? 

[stahta01]

When I go to properties on a file and tick "Use custom command to build this file" in Advanced tab, it will automatically tick "File is read-only" in General tab. Is this an intended behavior?  

If the file is read only (Operating System Setting), yes it is the intended behavior.

Tim S.

[scarphin]

When I go to properties on a file and tick "Use custom command to build this file" in Advanced tab, it will automatically tick "File is read-only" in General tab. Is this an intended behavior?  

If the file is read only (Operating System Setting), yes it is the intended behavior.

Tim S.

I am also experiencing this and unfortunately the files are not read only. I think that's a bug.

[oBFusCATed]

It is a bug...

[oBFusCATed]

Should be fixed in trunk.

[Static]

What about #include filenames completion? This feature seems to work sometimes and sometimes it doesn't.
Assume I want to include the file at "../dialogs/CustomDialog.h"
So, I type:
#include "../d" (note the closing quote mark)
and here comes CC suggesting "../dialogs/CustomDialog.h". I press 'enter' and get
#include "../dialogs/CustomDialog.h"" (extra quote mark)
or even
#include "../d../dialogs/CustomDialog.h" (my input wasn't overwritten)
But sometimes headers completion works perfectly.
Should this be reported as a bug?

[oBFusCATed]

fIf you can provide simple project and the exact steps to reproduce it - the yes report it as a bug.