The 31 march 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 31 March 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_20060331_rev2285_win32.7z
  - Linux :
         http://download.berlios.de/codeblocks/CB_20060331_rev2285_ubuntu.deb
         http://download.berlios.de/codeblocks/CB_20060331_rev2285_fc4.rpm (not yet)

Resolved Fixed:

• (wxSmith redesign:
  * spacer and sizers are back to the business
  * Small extension to enum Property (value can be stored in xml using integer or name)
  * Temporary hacks to wxsDrawingWindow (temporarily disabled overdrawing, it's not yet working and hide some important things)
  * Added wxsLANGMSG macro for reporting unsupported coding language (all sources converted to use them)
  * wxsParent::GetChildExtra changed to public
  * wxsSizer doesn't threat wxsSpacer as special case now (code moved to wxsSpacer class)
  * Fixed some doxygen warnings
  * Added doxygen howto - deriving from wxsItem (other classes will be soon)
  * Added missing SetupWindow() if dialog frame and parent (colours, fonts etc. are now set up properly in editor)
  * Moved some sizer setting-up code for wxsContainer to wxsSizer class
  * Fixed background color bug in sizer preview)
• Plugins can now add their own configuration page in the project properties dialog. No plugin makes use of this yet.
• Plugin SDK version updated to 1.6.13
• Correctly update debugger breakpoints when adding/removing lines in the editor (used to keep the old breakpoint lines in memory)
• ixed creating a new compiler by copying an existing one (would throw an exception after the first copy)
• Fixed a crash in linux when entering environment settings (patch #973)
• Fixed toolbars size problems with wx2.6.3 (patch #972)
• Added editor settings for caret width and color (adjusted patch #968)

Regressions/Confirmed/Annoying/Common bugs:

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

wx 2.6.3 trial build
A link to the unicode windows wxWidgets 2.6.3 dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26u_gcc_cb_wx2.6.3.7z
And CB :
- Windows : http://download.berlios.de/codeblocks/CB_20060331_rev2285_win32_wx2.6.3.7z

[orefa]

The Win32 package gives "File doesn't exist". The Ubuntu package downloads.

[orefa]

Scratch that, it's ok now. Timing is everything.

[Conan Kudo]

Uhh, the IDE is using wxWidgets 2.6.2 instead of 2.6.3! And if it supposed to use wx 2.6.3, it should have ANSI and Unicode DLLs...

[TDragon]

Uhh, the IDE is using wxWidgets 2.6.2 instead of 2.6.3! And if it supposed to use wx 2.6.3, it should have ANSI and Unicode DLLs...

Nothing stopping you from compiling C::B for wxWidgets 2.6.3 yourself...

[Conan Kudo]

Uhh, the IDE is using wxWidgets 2.6.2 instead of 2.6.3! And if it supposed to use wx 2.6.3, it should have ANSI and Unicode DLLs...

Nothing stopping you from compiling C::B for wxWidgets 2.6.3 yourself...

Two webservers running in virtual machines and a MySQL installation says otherwise... I cannot stop them since I do a lot of website testing on my computer... I'm just wondering why it was built for wx 2.6.2 if the problems were corrected for wx 2.6.3..

[takeshimiya]

I'm just wondering why it was built for wx 2.6.2 if the problems were corrected for wx 2.6.3..

Come on, the wx 2.6.3 toolbar layout problems was fixed yesterday (or today). You really expect that Lieven which is very busy with it's travels to compile wx 2.6.3 which takes time, all in one day? :?

[Conan Kudo]

Oh.. Sorry, I thought that he just tells it to do it and leaves... I didn't realize he may actually stay there the whole time!! :shock: Oh, and killerbot's name is Lieven?? :shock:

[EricKane]

Fixed toolbars size problems with wx2.6.3 (patch #972)

The toolbars size problems with wxwindows 2.6.3 still exist in main toolbars.

[killerbot]

I am back guys, I landed back in Belgium yesterday evening late.

Build plans for this weekend :
- official nightlies (wx 2.6.2)
- a new special build with wx 2.6.3
- a new ansi builds for our win9x friends

Cheers,
Lieven

[Zingam]

I wonder when the developers will add the following features:

1. A toolbar with a Save Project button and Save Workspace button
2. A right-click option on a workspace: Add a new project
3. Change the icons for Find & Replace with icons that are more expressive what thay do.



4. Improve the Find & Replace dialogs?


Is the bug that crashes CB on linux when moving the toolbars already fixed?

[killerbot]

2. A right-click option on a workspace: Add a new project

Good idea, just thinking out loud (no promise for implementation though) :
- add new project --> boots up the new project commands
- add existing project  --> boots up the open project commands
Names : add existing project, or open project ?? In this case I think the "add" is better : consistency for new and existing.

[thomas]

I wonder when the developers will add the following features:

1. A toolbar with a Save Project button and Save Workspace button
2. A right-click option on a workspace: Add a new project
3. Change the icons for Find & Replace with icons that are more expressive what thay do.

Not any time soon, possibly never.

First, the topics in the nightly builds forum are neither for bug reporting, nor are they for feature requests. Even though we have occasionally (out of pure amiability) reacted to bug reports in here, we will probably not do so with feature requests.
Second, those are features which are not really needed, but which nevertheless carry a few dependencies and may introduce new bugs/problems.

We already have more than enough to do at the present time with things that are needed, and we will have enough new bugs appearing with the necessary changes taking place in the next weeks. Staying on schedule with what we have to do so far is already mission impossible.

[Zingam]

I see. So it also means that the interface won't be customizable too, does it?

[thomas]

It is, partially (via the wxKeybinder plugin) and it will be (generally supported by the core application). Only just not now.

Although the action-based, fully customizable event system is practically ready for use, there is no way we could release it before version 1.0, as we did not have and do not have the time to thoroughly test it. You wouldn't want us to release code which we are not at least 99% certain of, would you.
If you look at the roadmap, you will see that we already have an almost unreasonably tight schedule. We will only have 1-2 weeks to test all the changes that we have planned for the final release before meeting release date. Actually, that is pure madness, but we don't have a choice, tempus fugit...