The 31 august 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://prdownload.berlios.de/codeblocks/wxmsw26u_gcc_cb_wx2.6.3p2.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10.7z

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

The 31 August 2006 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20060831_rev2936_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20060831_rev2936_Ubuntu6.06.deb
         http://prdownload.berlios.de/codeblocks/CB_20060831_rev2936_fc4+5.rpm


Resolved Fixed:

• CodeCompletion toolbar added which allows to jump to functions of the current editor and also tracks in which function your cursor is (view->toolbars->codecompletion)
• Symbols browser now keeps the special folders with globals on top, when sorting
• Symbols browser doesn't display container tokens (namespaces, classes, enums) in the bottom list
• Fixed bug in symbols browser which would show a + in front of classes even if no children (especially when option to show inheritance is enabled)
• Each of the special folders (globals) in the symbols browser is coloured gray if it contains no tokens
• Fixed (improved) "current file's symbols" symbols browser's view filter
• Build options -> "Project/Target change with changed settings" dialog changed to AnnoyingDialog
• compilergcc - "Abort Build" : for WXMSW only : write logmessage before skipping the rest of the logstream,
    it can take a while, until gcc stops the actual build. no change for Linux build
• batchbuild log window auto-closes even when an error occurred during the build,
    if the option --no-batch-window-close was not given

Regressions/Confirmed/Annoying/Common bugs:

• toolbar-images-not-changing-state (is a wx problem/Win XP problem)
• menu items with icon not correctly aligned (since wx263)

[kelo81]

Hello everybody, I remarqued that since yesterday the "there are several issues with Code Completion (is being redesigned : work in progress)" dissapeared from the "Regressions/Confirmed/Annoying/Common bugs:" list.
My question is: Is the Code Completion now 100% stable?, if that's the case, I will be very very happy!! (the point is that I didn't have the time to test it myself).
Anyway, congratulations!!!!! 

[killerbot]

Hello everybody, I remarqued that since yesterday the "there are several issues with Code Completion (is being redesigned : work in progress)" dissapeared from the "Regressions/Confirmed/Annoying/Common bugs:" list.
My question is: Is the Code Completion now 100% stable?, if that's the case, I will be very very happy!! (the point is that I didn't have the time to test it myself).
Anyway, congratulations!!!!! 

very well noticed. Yes, I think we can say Code Completion has improved very very much. There are still some limitations to the parser, still some bugs in the parser. But every day some of these bugs are getting squashed. People, really, try out the code completion. If you have some problems, please try to isolate them in litlle projects you can give to use for debugging.

[nzoltan]

svn:2936

After I open ANY from my already existing projects, atfer the parser thread finish (cpu usage falling to nearly zero) the C::B enter an INFINITE LOOP with hourglass cursor.

[nzoltan]

Edit->Show call tip (Shift+Ctrl+Space) menu is it done?

[mandrav]

After I open ANY from my already existing projects, atfer the parser thread finish (cpu usage falling to nearly zero) the C::B enter an INFINITE LOOP with hourglass cursor.

Although you give no info at all, I know this is a bug of the linux version. I hadn't had the time to look into it yet, but will do this weekend.

Edit->Show call tip (Shift+Ctrl+Space) menu is it done?

How do you expect this to work when the IDE freezes?

[nzoltan]

After I open ANY from my already existing projects, atfer the parser thread finish (cpu usage falling to nearly zero) the C::B enter an INFINITE LOOP with hourglass cursor.

Although you give no info at all, I know this is a bug of the linux version. I hadn't had the time to look into it yet, but will do this weekend.

I use the C::B on Fedora Core 4. up to r2921 C::B nigthly build did works fine for me.

Edit->Show call tip (Shift+Ctrl+Space) menu is it done?

How do you expect this to work when the IDE freezes?

This is just a question because the "cc redisign" entry is removed from the red list on the top of this page, and beacuse I can`t try this at moment because the IDE freezes.

[squizzz]

Incorrect combobox drawing within toolbars under Windows 2000 is known problem, but unfortunately with this release it becomes somehow more annoying: screenshot (CodeCompletion toolbar is heavily affected). You may add this one to "Regressions/Confirmed/Annoying/Common bugs" list if you feel it feasible.

There is also some quite funny bug with Symbols browser when you turn on "Show inherited members". If there is a class (say ClassA) that has some inheritance relation with other class (ClassB), then it's possible to expand tokens like this: ClassA->Base classes->ClassB->Derived classes->ClassA->Base classes->ClassB->Derived classes->ClassA... etc up to infinity. This one is not platform specific though.

[yaustar]

Incorrect combobox drawing within toolbars under Windows 2000 is known problem, but unfortunately with this release it becomes somehow more annoying: screenshot (CodeCompletion toolbar is heavily affected). You may add this one to "Regressions/Confirmed/Annoying/Common bugs" list if you feel it feasible.

I have that problem as well. Seems to be fine on XP but my 2000 machine it looks exactly the same as the screenshot above even though they are the same build.

Build: Jun 23 2006, 19:44:03 - wx2.6.3(Windows, unicode)

[skirby]

I have exactly the same problem here.
It exists since several months.

But, like mandrav say:
Be patient!
This bug will be fixed soon...

I hope 

[mandrav]

Is there anyone here who is running win2000 and builds C::B from source?
It's hard to fix this annoying display bug without having access to this OS...

[nix_BB]

I have a machine running 2000 and can build from source- If you have any particular instructions I'll be happy to help. I'll not be available for the next 7 hours, but after that I'm all yours.  :wink: :oops:

[mandrav]

I have a machine running 2000 and can build from source- If you have any particular instructions I'll be happy to help. I'll not be available for the next 7 hours, but after that I'm all yours.  :wink: :oops:

Great news!
When you have everything setup (C::B built from source and up'n'running), PM me .

[kkez]

Mandrav, you can test it by yourself by removing the manifest file under windows XP
BTW, the same problem exists under windows 98 and ME.

[PMike]

• CodeCompletion toolbar added which allows to jump to functions of the current editor and also tracks in which function your cursor is (view->toolbars->codecompletion)

Wow, COOL! This is feature I waited so long! Thanks!!!
PS. It works even with namespaces

[Kreso]

• CodeCompletion toolbar added which allows to jump to functions of the current editor and also tracks in which function your cursor is (view->toolbars->codecompletion)

Wow, COOL! This is feature I waited so long! Thanks!!!

agreed!

I say, hip hip, hoooray! for the development team

[Alturin]

*Cheer*
Jay for the devs!
C::B is becomming more and more everything I want from an IDE, you guys are great!

[wvdakker]

Still one thing is missing .....  SVN integration....  :?

But C:B is an excellent piece of work... 

[PsYhLo]

wait for now the most important thing is to release RC3 and final for now

isn't that right

[marfig]

It sure seems close.
My guess is that you good people went far more ahead of what you thought at first when it was initially announced. Which is good, if someone asks me. There is no hurry when the constant development is widely available through working nightly builds.

There is only one thing I'm missing in C::B. The ability to view two different files in split view.

[PsYhLo]

There is only one thing I'm missing in C::B. The ability to view two different files in split view.

it's a good idea

[Alturin]

I tried out the code-completion bar thingy, and it's so fast! Great!
Only thing, what's with the greyed-out bar left of the other one? Do the global functions go there? If so, how do I turn that on?

What would be a superb improvement is the ability to type in the first part of the function's name in that toolbar, like in symbol view, save for that, it's supberb!

[killerbot]

I tried out the code-completion bar thingy, and it's so fast! Great!
Only thing, what's with the greyed-out bar left of the other one? Do the global functions go there? If so, how do I turn that on?

What would be a superb improvement is the ability to type in the first part of the function's name in that toolbar, like in symbol view, save for that, it's supberb!

the left bar wil be enabled inthe future and will have the following functionality :

1) it tracks the class (and namespace) of the method the cursor is in (now : it's class OR if no class it shows the namespace)
2) if you select an entry from it, that will act as a filter on the possible selections in the right choice control, and once you click again in the editor it goes back to normal usage showing all entries

[Last-Attacker]

I saw with code completion that it no longer brings up the member list list-box for wxWidgets class member and methods (when you type '.' or '->' after a widget object such as a wxStatusBar object).
It works well with the local project classes, etc. but I really like (and need) it to bring up the libraries' classes that you've included into your project. It also seems not to include the std classes like std::vector for the member list list-box.

EDIT:
I left the IDE for a couple of minutes (like 10  :wink: ) and it's not like the parser didn't have enough time to look it up I believe.
But I also saw that classes inheriting from libraries's classes is picked up (code-completion) but only the members and methods that are defined for your class.

The scope thing seems to work ok though.
Good job also with the other code completion additions!

[Phatency]

I can't open symbols browser anymore. It simply does not open. I've tried fresh-installing cb with no luck.
Version 1.0 revision 2936 ()   gcc 3.4.5 Windows/unicode
WinXP SP2

[Vampyre_Dark]

I can't open symbols browser anymore. It simply does not open. I've tried fresh-installing cb with no luck.
Version 1.0 revision 2936 ()   gcc 3.4.5 Windows/unicode
WinXP SP2

Same thign appeared to happen to me too. But it was docked by default as a tab in the project manager. I had to set it to be a free floating window again, and I docked it back the old way.

[PDEE]

Same thign appeared to happen to me too. But it was docked by default as a tab in the project manager. I had to set it to be a free floating window again, and I docked it back the old way.

I never thought of undocking it  . I prefer it the old way aswell. Not enough room in the project manager place. Why was it moved?

[Phatency]

I can't open symbols browser anymore. It simply does not open. I've tried fresh-installing cb with no luck.
Version 1.0 revision 2936 ()   gcc 3.4.5 Windows/unicode
WinXP SP2

Same thign appeared to happen to me too. But it was docked by default as a tab in the project manager. I had to set it to be a free floating window again, and I docked it back the old way.

Oh right, that's it, it's already tabbed Well, the view-menu certainly should do something when it's selected to avoid these kind of misunderstandings..

Actually, should it even be in the view-menu when it's not a dockable window, but a tab of manager instead?

[takeshimiya]

Actually, should it even be in the view-menu when it's not a dockable window, but a tab of manager instead?

The real solution to all of this problem will come from wxAUI and "tear-able tabs". It's on the roadmap already.

If you don't know what "tear-able tabs" are, see it in action for example in wxIFM: http://snakesoft.net/wxifm/demo.zip

EDIT: and wxAUI tabs, http://www.kirix.com/res/aui/auitabs.exe

The thread is here: http://www.kirix.com/community/forums//viewtopic.php?t=169

[takeshimiya]

About the wx2.6.2 vs. 2.6.3 toolbar size problems:

The problem is as follows. In wxWidgets 2.6.3, the toolbar's initial client size (when wxDefaultSize) is specified no longer is set to the toolbar's minimum acceptable size. This is slightly different behavior than 2.6.2.

To fix this problem, we added code that sets toolbar initial toolbar sizes to whatever wxToolBar::GetBestSize() returns. Unfortunately, the size that is being returned by the class is too small (vertically). I don't know why.

At any rate, the way to get around this is to do your own wxToolBar::GetBestSize() call, then specify this size on your AddPane call with the BestSize parameter, while at the same time increasing the y parameter by the number of missing pixels.

I hope that wxToolBar::GetBestSize() on win32 can be fixed soon.

Either that, or you can check out the code that is doing the wrong calculation. It's called from wxAUI 0.9.2 on line 1293.

All the best,
Ben

[severach]

Bug: When you first run CB, you get a compiler box. If you select one, you get a [Default] button. If you select several ... wait, how could you set several compilers to the default? That listbox shouldn't be multiselect.

Bug: When importing old projects, they must be detected by compiler number. Now that VS 2005 has been inserted, all compilers below that are now shifted by one. For example, my Borland C++ 5.5 projects are switched to VS 2005.

Configuration things that still need fixing with some excerpts from my C::B 1.0 RC2 .reg file:

The Platform SDK isn't detected and automatically added to the MSVT 2003 bin, include, lib, and resource-include folders. You might also add the %SDK%\Bin\win64 folder to the MSVT 2003 bin folder to cover up the CVTRES and LIB bug as described in the wiki. VS 2005 does get the SDK folders auto added so copy that code.

Borland-C++ 5.5: You are still using brcc32.exe which is completely defective and compiles very few modern .rc files. Please change it to the one in the SDK if available. Copy the command line from MSVT 2003.
"res_compiler"="c:\\Program Files\\Microsoft Platform SDK\\Bin\\RC.Exe"
"Compile Win32 resource file"="$rescomp $res_includes -fo$resource_output $file"

Borland-C++ 5.5: Link to Dynamic Library is a non working command line. This is as close as I can get. The .BCDEF file needs to be created manually and should in the future be created by Code::Blocks.
"Link object files to dynamic library"="$linker -Tpd $link_options $libdirs c0d32 $link_objects, $exe_output,, $libs,$exe_output.BCDEF, $link_resobjects"

DMC: The included RC compiler is no good. Use the same one as MSVT and BC above if available.
DMC: The SDK include & resource (not lib) should be added to the DMC folders.
Neither linker line works at all.
"Link object files to executable"="$compiler -L/subsystem:windows -WA -mn $link_options $link_objects -o $exe_output $libs $link_resobjects"
"Link object files to dynamic library"="$compiler -L/subsystem:windows -WD -mn $link_options $link_objects -o $exe_output $libs $link_resobjects"

OWC: Compiler Options: -3s. Noone is expecting register calling and Windows OWC libraries don't support it.
Linker: link386.exe
Since OpenWatcom and Borland-C produce exports names so far outside of the norm, the BCDEF file needs to be created to keep them in line.
"Link object files to dynamic library"="$linker -nologo -dll -out:$exe_output $libs $link_objects -def:$exe_output.BCDEF"

My command lines aren't perfect but they are a functional improvement over what is mostly non functional.

[nix_BB]

The following code based on Takeshi's post has no effect, although I'm not sure if I've put it in the correct place.

Hopefully Mandrav will get out of bed soon and help figure this out.

Code

bool CodeCompletion::BuildToolBar(wxToolBar* toolBar)
{
    wxSize sz;

    Manager::Get()->AddonToolBar(toolBar,_T("codecompletion_toolbar"));
    m_Function = XRCCTRL(*toolBar, "chcCodeCompletionFunction", wxChoice);
    m_Scope = XRCCTRL(*toolBar, "chcCodeCompletionScope", wxChoice);
    m_Scope->Disable();
    toolBar->Realize();

    // Trying to fix toolbar hSize bug
    sz = toolBar->GetBestSize();
    sz.x += 30;
    toolBar->SetBestFittingSize(sz);

    return true;
}

EDIT: Ok I was fiddeling in the wrong place.... The following code yeilds results but does not fix the bug. It merely shows an additional 30 pixels of the toolbar- hence the problem lies in GetBestSize. Anyone know another method of determinnig the minimum size of a toolbar?

Code

void MainFrame::DoAddPluginToolbar(cbPlugin* plugin)
{
    wxSize size = m_SmallToolBar ? wxSize(16, 16) : wxSize(22, 22);
    wxToolBar* tb = new wxToolBar(this, -1, wxDefaultPosition, size, wxTB_FLAT | wxTB_NODIVIDER);
    tb->SetToolBitmapSize(size);
    if (plugin->BuildToolBar(tb))
    {
        SetToolBar(0);
        wxSize sz;
        sz = tb->GetBestSize ();
        sz.x+=30;
        sz.y++;
        tb->SetBestFittingSize(sz);

        ... 
    }
    ...
}

[sque]

svn:2936

After I open ANY from my already existing projects, atfer the parser thread finish (cpu usage falling to nearly zero) the C::B enter an INFINITE LOOP with hourglass cursor.

I can confirm same bug from a clean svn rebuild. (2937)

[Kazade]

I'm having lots of problems with the last 2 builds, I've had to downgrade to the build of the 29th August (and even then C::B crashes when I save as I mentioned before)

With the builds of the 30th and 31st C::B is crashing after about 10 seconds, I cant find a common cause it will just either, lock up with a timer, or in the case of the 31st build, send me into an infinite loop of debug crash handler windows all of which are also frozen.

It might be something to do with the symbols browser being integrated into the tabbed left bar as it only moved to there on the build of the 30th, downgrading to the 29th put it back where it was and I get no more unexplained crashes.

When is C::B going to go into a feature freeze and just focus on bug-fixes? It already has enough features for version 1 IMO far more than any other free IDE. The more features added just add more bugs and reduces stability, don't get me wrong I love C::B and the work you guys do is amazing, but it might be time to focus on bugs rather than features.

Luke.

[Kazade]

On other thing, I don't know if its just me, but the fonts in C::B aren't anti-aliased, is there a way to turn this on? I'm running on Kubuntu.  I've tried changing the font settings to match those in Kate, but the text is still blocky and I cant tell the difference between a . and , or : and ; which is really frustrating.

[Alturin]

If I read the board right, the CodeCompletion upgrade wasn't done by the usualy C::B devs, but some cool guy with way too much skills and time ^^.

[mandrav]

If I read the board right, the CodeCompletion upgrade wasn't done by the usualy C::B devs, but some cool guy with way too much skills and time ^^.

Well, you read wrong.
The cool-guy-with-way-too-much-skills-and-time has provided a different standalone implementation (i.e. not a C::B plugin).

[Kazade]

On other thing, I don't know if its just me, but the fonts in C::B aren't anti-aliased, is there a way to turn this on? I'm running on Kubuntu.  I've tried changing the font settings to match those in Kate, but the text is still blocky and I cant tell the difference between a . and , or : and ; which is really frustrating.

I fixed this, I realised that the same thing was happening to other GTK programs.. it is a bug in KDE, if anyone else experiences this.. in the KDE font settings change General to any other font than the current one, apply, and then change it back again.

[Alturin]

If I read the board right, the CodeCompletion upgrade wasn't done by the usualy C::B devs, but some cool guy with way too much skills and time ^^.

Well, you read wrong.
The cool-guy-with-way-too-much-skills-and-time has provided a different standalone implementation (i.e. not a C::B plugin).

Heh, that makes you a cool-guy-with-way-too-much-skills-and-time too then? But I guess we already knew that ;P


[EDIT]
I found this in the change logs:
* Added handling of #if[[n]def] preprocessor blocks in code-completion's parser. Currently it accepts the #if part and ignores from the #el[se|if] (if it exists) up to the #endif. The special case "#if 0" will be handled later.

Does the fact that it ignores the #el[se|if] currently cause this (file is here)?

[/EDIT]

[killerbot]

Bug: When you first run CB, you get a compiler box. If you select one, you get a [Default] button. If you select several ... wait, how could you set several compilers to the default? That listbox shouldn't be multiselect.

fixed

[mandrav]

[EDIT]
I found this in the change logs:
* Added handling of #if[[n]def] preprocessor blocks in code-completion's parser. Currently it accepts the #if part and ignores from the #el[se|if] (if it exists) up to the #endif. The special case "#if 0" will be handled later.

Does the fact that it ignores the #el[se|if] currently cause this (file is here)?

[/EDIT]

Yes, and I 've fixed it (not committed yet).

[lubos]

sorry if this alredy known bug. i start cb, go to fullscreen mode and open script console:

[lubos]

hey and can someone  make plugin for visual c++ settings(.vssettigs) import? it can be nice thx

[Alturin]

[EDIT]
I found this in the change logs:
* Added handling of #if[[n]def] preprocessor blocks in code-completion's parser. Currently it accepts the #if part and ignores from the #el[se|if] (if it exists) up to the #endif. The special case "#if 0" will be handled later.

Does the fact that it ignores the #el[se|if] currently cause this (file is here)?

[/EDIT]

Yes, and I 've fixed it (not committed yet).

My guess'd be you haven't had the time to commit it yet? It'd be really great if this was fixed 

[mandrav]

My guess'd be you haven't had the time to commit it yet? It'd be really great if this was fixed

This fix is part of another bigger patch which needs a lot of testing before committing... It will come, don't worry .

[Alturin]

My guess'd be you haven't had the time to commit it yet? It'd be really great if this was fixed

This fix is part of another bigger patch which needs a lot of testing before committing... It will come, don't worry .

Way cool, I'll be keeping a close eye on the changelog I guess ^_^.
Keep up the great work