The 21 July 2012 build (8150) 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_gcc452-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_gcc452-TDM.7z

The 21 July 2012 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20120721_rev8150_win32.7z
  - Linux :
   none

Resolved Fixed:

• debugger: Added support for parsing watches returned by the python printing
• codestat: Select any project or entire workspace to get statistics (patch #3271, thanks sbezgodov)
• applied patch by stahta01 to reduce #defiens needed for compilation of wxPropGrid (see here: http://forums.codeblocks.org/index.php/topic,15938.msg107359.html) -> use was in-consequent anyways
• updated wxScintilla core to integrate a patch of darmar (for scintilla) to fix Fortran indention
• wxScintilla now uses wxFFile for loading and saving (like wxWidgets), if available (should speed up file operations a little)
• applied patch #3304: Move line(s) up/down (shortcut)
• fixed accelerators used twice in main menu
• applied patch #3305: Replace all: Use Freeze/Thaw (increases speed)
• edit watched resource: removed obsolete sub-resource "dlgEditWatches" (only "dlgEditWatch" is used)
  - made dlgEditWatch resizable
• include lower capital "warning" message in GDB's ignore list
• fixed a crash but in MSVC 10 loader
• updated Windows project files so they work if "devel" output folder and sub-folder do not exist yet
• updated Windows project files for easier debugging of plugins
• added EditorConfig plugin
• fixed certain project files on Unix
• added Code::Block Unix workspace file (=Code::Block project file + Contrib plugins workspace)
• first update of C::B installer script (not yet complete)
• second update of C::B installer script (probably complete? - needs testing!)
• applied patch #3238: Remove a lot compiler warnings (unused vars; signed/unsigned)
• updated (wx)Scintilla to 3.2.1 also fixing wxSmith folding
• EditorConfig-plugin (linux): fix error in Makefile.am, that prevents the plugin from being build with automake-system
• EditorConfig-plugin (linux): fix for make dist
• updated wxPdfDocument to v0.9.3 (for source exporter plugin), also to fix some memory leaks and font issues
• wxSmith new window dialog: clarify options and don't use member variables if not needed
• wxSmith: implemented ability to select specific wxValidator's (other than wxDefaultValidator) for all widget classes
• wxSmith: Fixed a bug with float values on some locales, based on a patch
• add ability to hide the editor tabs, can be toggled with "View -> Hide editor tabs" or "Ctrl+H"

Regressions/Confirmed/Annoying/Common bugs:

[jens]

As usual:
Debian packages (binaries and sources) for 32-bit and 64-bit systems can be found in my debian-repo.
Fedora packages (binaries and sources) for 32-bit and 64-bit systems (fc15, fc16 and fc17) can be found in my rpm-repo .

Important note for debian (and ubuntu) users:
I changed the layout of my debian-repo, to fix the issue described in this thread:
http://forums.codeblocks.org/index.php/topic,16357.msg110806.html#msg110806
Please (re)read the instructions on my website, and fix your entries in /etc/apt/sources.list[.d] accordingly.

RedHat/CentOS 5 and 6 packages will follow.

[damorin]

Hi.

the syntax highlighting for the C/C++ keyword was not using my selected foreground color (my setting is yellow on black background),  in the editor all keywords were dark blue (but all other setting were OK, including background).

When I clicked on the foreground to set again with the same yellow, the keywords were back to the correct color. This is looking like a default setting not updated correctly.

WinXP Build 8150.

[savya]

I'm having trouble with syntax highlighting with this new build 8150 on Windows 7. On my system all the keywords appear black, braces & parenthesis appear highlighted and user keywords appear bold red. It seems it did not pick up my previous "syntax highlighting" settings correctly.

[MortenMacFly]

For those with the syntax highlighting issue: I don't understand what you mean. Screenshot? Steps to reproduce?

[jens]

Nighly packages for RedHat/CentOS 5 and 6 are now available from my rpm-repo .
You need additional packages from other repos, see my site for details.

[savya]

Screenshot from build 8150:  http://flic.kr/p/cBFsiC
Screenshot from build 8086:  http://flic.kr/p/cBFsmC

I have included herewith the screen shots of the "syntax highlighting" issue with the latest build (8150) on Win7. I experienced this problem from the moment I installed the latest nightly build and began using it. I have also included a screen shot from the previous build (8086) for comparison. I hope this helps. Please let me know if you need more information.

P.S.- I am thankful to the C::B team for producing this simple, elegant and "free" IDE. I have been using it for a long time and I'm in love with it. Since this has been the first time that I have involved myself in the C::B forums, I wanted to express my gratitude to the developers. Keep up the good work.

[cacb]

The Windows version of 8150 has a significant issue in that all the wxSmith RAD editor images are missing. This makes wxSmith unusable since all the standard button images are replaced by text which is much wider and thus hidden by a scrollbar. See attached.

Linux *.deb variant of 8150 from Jens is OK in this regard.

On Windows I was able to fix the wxSmith problem locally, by copying the wxSmith image folder (missing in 8150) from Nightly Build 8086. Observe that there appears to be other images subfolders missing also, see attached screenshot.

[MortenMacFly]

I hope this helps. Please let me know if you need more information.

Can you export your colour scheme using cb_share_config an provide it here, please?

To be honest: I have no glue what should have cause this. IMHO we were not doing any changes in that field.

[savya]

I hope this helps. Please let me know if you need more information.

Can you export your colour scheme using cb_share_config an provide it here, please?

To be honest: I have no glue what should have cause this. IMHO we were not doing any changes in that field.

I have attached a 7z file containing the editor color scheme.

[Vuki]

This change in lexer_cpp.xml:

Code: [Select]

                <Style name="Comment (normal)"
                        index="1,23"
                        fg="160,160,160"/>

is causing problems. When i changed it back to the previous form:

Code: [Select]

                <Style name="Comment (normal)"
                        index="1"
                        fg="160,160,160"/>
the highlighter works correctly. The added ",23" part borks the highlighter and causes it to select colors from wrong entries.

[carra]

Apart from what Vuki said, it might have something to do with the update to the new Scintilla 3.2.1.

[trivia21]

I'm using svn 8162 under linux and have a problem with syntax highlighting as well.
The "Keyword" option changes the color of numbers, while I need to use "User keyword" to change the color of keywords (int, char etc.). I can't remember if there was a "Numbers" menu item, but there isn't one right now.

[MortenMacFly]

This change in lexer_cpp.xml:

Code: [Select]

                <Style name="Comment (normal)"
                        index="1,23"
                        fg="160,160,160"/>


This is actually correct - style 23 refers to "wxSTC_C_PREPROCESSORCOMMENT", which shall be coloured like a normal comment therefore.

I wonder why I don't see this...?! Could it be that you simply didn't define this style?

[ptDev]

The unofficial installer for Windows has also been updated to match the same revision as the nightly build. Note that it is slightly unstable in comparison and includes a number of low-risk patches (meant for early testing by more users).

See a list of differences between the two here.