The 17 december 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 17 December 2006 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20061217_rev3392_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20061217_rev3392_Ubuntu6.06.deb
         http://prdownload.berlios.de/codeblocks/CB_20061217_rev3392_suse100+101.i586.rpm
         http://prdownload.berlios.de/codeblocks/CB_20061217_rev3392_fc4+5.i586.rpm


Resolved Fixed:

• KeyBinder 1.0.6 2006/12/14
  - Added code to remove stale dynamic menu items
  - Invoke MergeDynamicMenu() & OnSave() at plugin termination
  - In IsValidKeyComb() changed '+' to '-'
  - Disallowed single key cmdStrings in wxKeyMonitorTextCtrl::OnKey()
  - Reduced size of .ini fileName
  - Fixed broken OnKey() to accept function keys w/o Ctrl- Alt- or Shift-
  - Minor preparations for KeyMacs support

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)
• at startup keeps asking/detecting compilers

[yostane]

Each time I launch the program, I have to choose the complier, I'm under WinXP SP2. using this Nightly Build

[killerbot]

known problem, will be solved somewhere this week [that might even be tomorrow]

[yostane]

Do you use WxWidgets 2.8

[stahta01]

Do you use WxWidgets 2.8

Yes, you can compile programs that use WxWidgets 2.8 with CodeBlocks.
If you mean can you compile codeblocks and link it against WxWidgets 2.8, the answer is no for the current unpatched source.

Tim S

[killerbot]

no, we only support wx 2.6.x for the moment.

The thing is it seems a lot a code changes might be needed. I think we shall do them one by one.
But the big issue is : we need to make sure everything still works with 2.6x.

On windows it is very simple, we can provide a new wx dll and everybody code use new nightlies once those ore build against wx 2.8.

But on linux is a pain the .. to upgrade such a thing as wx, so I think only the next round of distributions will ship with wx 2.8.
And we also need to see, if wx 2.8 fixes bugs, and not just bring new ones [like wx 2.6.x brought several new ones !!!].

[killerbot]

others can confirm the following problem (I stumbled upon in Suse 10.2, checking in windows tomorrow) : settings menu -> edit startup script ==> errror message "Could not run script: edit_startup_script.script"

[killerbot]

just checking, but this is probably ok. Guess new since the new keybinder update. Opened a project [it didn't occur sooner] in Cb (linux) and got the following informational message "No keyprofiles have been found... A default keyprofile will be set."
and then CB crashes :-(

Code

<?xml version="1.0" encoding="utf-8"?>
<report version="1.0" kind="exception">
  <system description="Linux 2.6.18.2-34-default x86_64"/>
  <modules>
    <module path="/usr/local/bin/codeblocks" address="00400000" size="002a8000"/>
  </modules>
  <stack>
    <frame level="2" function="wxStackWalker::Walk(unsigned long)" offset="0000002b"/>
    <frame level="3" function="wxDebugReport::AddContext(wxDebugReport::Context)" offset="00000a70"/>
    <frame level="4"/>
    <frame level="5" function="wxFatalSignalHandler" offset="0000001c"/>
    <frame level="6"/>
    <frame level="7" function="cbKeyBinder::UpdateArr(wxKeyProfileArray&amp;)" offset="0000004a"/>
    <frame level="8" function="cbKeyBinder::OnLoad()" offset="00000551"/>
    <frame level="9" function="cbKeyBinder::OnEditorOpen(CodeBlocksEvent&amp;)" offset="000000cb"/>
    <frame level="10" function="wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&amp;, wxEvtHandler*, wxEvent&amp;)" offset="0000007f"/>
    <frame level="11" function="wxEventHashTable::HandleEvent(wxEvent&amp;, wxEvtHandler*)" offset="0000009f"/>
    <frame level="12" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="000000c6"/>
    <frame level="13" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="00000050"/>
    <frame level="14" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="00000050"/>
    <frame level="15" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="00000050"/>
    <frame level="16" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="00000050"/>
    <frame level="17" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="00000050"/>
    <frame level="18" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="00000050"/>
    <frame level="19" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="00000050"/>
    <frame level="20" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="00000050"/>
    <frame level="21" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="00000050"/>
    <frame level="22" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="00000050"/>
    <frame level="23" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="00000050"/>
    <frame level="24" function="cbEditor::NotifyPlugins(int, int, wxString const&amp;, int, int)" offset="000000e1"/>
    <frame level="25" function="cbEditor::Open(bool)" offset="00000357"/>
    <frame level="26" function="cbEditor::cbEditor(wxWindow*, wxString const&amp;, EditorColourSet*)" offset="0000038d"/>
    <frame level="27" function="EditorManager::Open(wxString const&amp;, int, ProjectFile*)" offset="000002ee"/>
    <frame level="28" function="cbProject::LoadLayout()" offset="00000555"/>
    <frame level="29" function="ProjectManager::LoadProject(wxString const&amp;, bool)" offset="000002ba"/>
    <frame level="30"/>
    <frame level="31"/>
    <frame level="32" function="MainFrame::OnStartHereLink(wxCommandEvent&amp;)" offset="000001f2"/>
    <frame level="33" function="wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&amp;, wxEvtHandler*, wxEvent&amp;)" offset="0000007f"/>
    <frame level="34" function="wxEventHashTable::HandleEvent(wxEvent&amp;, wxEvtHandler*)" offset="0000009f"/>
    <frame level="35" function="wxEvtHandler::ProcessEvent(wxEvent&amp;)" offset="000000c6"/>
    <frame level="36" function="wxEvtHandler::ProcessPendingEvents()" offset="0000005c"/>
    <frame level="37" function="wxAppConsole::ProcessPendingEvents()" offset="0000004e"/>
    <frame level="38"/>
    <frame level="39" function="g_main_context_dispatch" offset="000001b4"/>
    <frame level="40"/>
    <frame level="41" function="g_main_loop_run" offset="000001ca"/>
    <frame level="42" function="gtk_main" offset="000000a3"/>
    <frame level="43" function="wxEventLoop::Run()" offset="00000051"/>
    <frame level="44" function="wxAppBase::MainLoop()" offset="0000004b"/>
    <frame level="45"/>
    <frame level="46" function="wxEntry(int&amp;, wchar_t**)" offset="0000004c"/>
    <frame level="47"/>
  </stack>
</report>

[cstudent]

Ubuntu 6.10 (Edgy) build here.

[Grom]

What about CB for Linux 64 bit. Of cause I can install CB i586 on to my SUSE 10.2 64 bit. But other people probably may have troubles to do that.

[Pecan]

just checking, but this is probably ok. Guess new since the new keybinder update. Opened a project [it didn't occur sooner] in Cb (linux) and got the following informational message "No keyprofiles have been found... A default keyprofile will be set."
and then CB crashes :-(

Could you give the exact steps on how to recreate this?
Had there been a previous crash during CB initialization that would have corrupted the keybinder file?
Were two CB's running at the same time?
Was this the first run of the new CB with the keybinder changes?

Any clues would help.

thanks
pecan

[killerbot]

just tried it out on windows -> ok there, will have to redo the test this evening on linux [there it was reproducable], had builded CB, ran it, and the first time i opened a project I got that dialog box and crash. Note : on windows no dialog box at all.

[killerbot]

just checking, but this is probably ok. Guess new since the new keybinder update. Opened a project [it didn't occur sooner] in Cb (linux) and got the following informational message "No keyprofiles have been found... A default keyprofile will be set."
and then CB crashes :-(

Could you give the exact steps on how to recreate this?
Had there been a previous crash during CB initialization that would have corrupted the keybinder file?
Were two CB's running at the same time?
Was this the first run of the new CB with the keybinder changes?

Any clues would help.

thanks
pecan

After I had builded cb with the updated keybinder [in linux]. I start CB, all ok. The moment I opened a project, that message box pops up and I get the crash. I can still reproduce it.
Should I look more closely to a specific keybinder config file ?

[edit] : in my .codeblocks dir I have the following keybinder related files :
cbKeyBinder10.ini
cbKeyBinder10.ini0bak
cbKeyBinder10v111.ini
cbKeyBinder10v111.ini.bak

[Pecan]

. I start CB, all ok. The moment I opened a project, that message box pops up and I get the crash. I can still reproduce it.
Should I look more closely to a specific keybinder config file ?

[edit] : in my .codeblocks dir I have the following keybinder related files :
cbKeyBinder10.ini
cbKeyBinder10.ini0bak
cbKeyBinder10v111.ini
cbKeyBinder10v111.ini.bak

I have tried all morning to reproduce this error. With empty .ini's, missing .ini's etc etc, with no crash.

Would you zip up all those cbKeyBinder10* files and attach them to a msg here.
There may be something peculiar in those files.

thanks
pecan

[killerbot]

attached (remove the .txt extension)

[attachment deleted by admin]