The 18 april 2006 build is out.

[killerbot]

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml
A link to the unicode windows wxWidget dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26u_gcc_cb.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://download.berlios.de/codeblocks/mingwm10.7z

For support of ansi builds, a link to the ansi windows wxWidget dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26_gcc_cb.7z

The 18 April 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_20060418_rev2360_win32.7z
  - Linux :
         http://download.berlios.de/codeblocks/CB_20060418_rev2360_ubuntu.deb
         http://download.berlios.de/codeblocks/CB_20060418_rev2360_fc4+5.rpm

Resolved Fixed:

• Added Autosave to CodeBlocks-unix.cbp
• Added more file extension constants in FileFilters (including the dot this time)
• Exposed file extension constants to scripts
• Changed ScriptingManager::Load() to just load the script and not run it. Use ScriptingManager::Compile() afterwards to compile and run the script(s). Or use ScriptingManager::LoadAndRunScript() that works like Load() used to
• SDK version changed to 1.7.14
• Added new plugin: "Project wizard". It uses scripting to define wizards. See plugins/projectwizard/resources for more
• Added checkboxes in new project dialog, to filter showing the old file-based templates and the new wizard-based ones
• Fixed wrong paths in ProjectWizard 's Makefile.am files
• Increased width of new project dialog to old setting (again)
• ProjectWizard : little include fix
• Fixed a couple of build issues for *nix (regarding the projectwizard
  plugin)
• Fixed script errors in the new "D application" wizard

Regressions/Confirmed/Annoying/Common bugs:

• toolbar-images-not-changing-state (is a wx problem/Win XP problem)
• there are several issues with Code Completion (is being redesigned : work in progress)

[killerbot]

and here's the ansi build :
http://download.berlios.de/codeblocks/CB_20060418_rev2360_win32_ansi.7z

[Zingam]

Fixed script errors in the new "D application" wizard

-------------- Build: Debug in jhhhh ---------------
Compiling: hello.d
Error: unrecognized switch '-Wall'
Process terminated with status 1 (0 minutes, 0 seconds)
0 errors, 0 warnings


Any ideas where this switch -Wall is from?
 

[MedO]

-Wall stands for "enable all warnings" with gcc. It seems your d compiler doesn't understand the switch, so try to untick the corresponding checkbox in the compiler settings. Don't know if this is a C:B problem.

[killerbot]

Fixed script errors in the new "D application" wizard

-------------- Build: Debug in jhhhh ---------------
Compiling: hello.d
Error: unrecognized switch '-Wall'
Process terminated with status 1 (0 minutes, 0 seconds)
0 errors, 0 warnings


Any ideas where this switch -Wall is from?
 

What did you use : Digital Mars D or the GCC D ?

[skirby]

Hello,

Here is a simple example which show you a bug with the debugger (with that build and probably previous one)

You can find the project here:
http://www.badongo.com/file/498569

Debug the program.
You should have a screen like that


Now if you trace the following instruction:  strcpy(sStr, "azéerty");

All buttons of the debugger toolbar become disabled.


I really hope you could fix that problem.

Thanks and have a nice day

[Szabadember]

The same bug here!!!
If you watch strings with non-english characters (áéűőúüöó for example), all buttons in the debug menu become disabled.

I've encountered another bug: if you clear all breakpoints with the command 'Clear all breakpoints' in the debug menu, the red circles do not disappear.

[MoonKid]

ansi build

The editorsettings-crash-bug is still alive in this version.

[MortenMacFly]

The same bug here!!!
If you watch strings with non-english characters (áéűőúüöó for example), [...]

I tried to debug that bastard. That's unfortunately some "deep-level stuff". When the event DebuggerGDB::OnGDBOutput is fired from the piped process the event.GetString() already holds the wrong string. So it must be related to the way how stdout and stcerr are obtained / converted in PipedProcess. I'm currently inspecting cbTextInputStream::ReadLine() and cbTextInputStream::NextChar() which could be the cause. I'm reporting this for those who may have more knowledge than I...
With regards, Morten.

Edit: That's really strange... if I inspect the memory of the string using C::B it clearly shows the "right stuff", passing a "display mystring.c_str()" to gdb seems to work, too. Hence it could be the way how STL strings are parsed in the debugger script (gdb_types.script)...?! Anybody else working on that can help?!