User forums > Nightly builds

The 24 May 2006 build is out.

(1/3) > >>

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

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 24 May 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_20060524_rev2499_win32.7z
  - Linux :
         http://download.berlios.de/codeblocks/CB_20060524_rev2499.deb
         http://download.berlios.de/codeblocks/CB_20060524_rev2499_fc4+5.rpm


Resolved Fixed:


* wxSmith redesign:
 * wxsWindowEditorContent stores wxsTtem->wxWindow* map. That increased code security.
 * Added data correction (with filling empty properties) when importing XRC file
 * Some other small code changes (code cosmetics)
* Fixed debugger's watches broken parsing when { or } appeared inside single-quotes (i.e. "{" worked fine where '{' would fail)
* Fixed and improved DebuggerTree::FindCharOutsideQuotes() to correctly account for single/double quotes and all combinations of one inside each other
* Don't show messages about upgrading the project file (and so don't mark it dirty), if program runs in batch-build mode
* Added more information text in "Settings->Compiler and debugger->Batch builds" page
* Added option in editor's margin settings to allow adding/removing breakpoints by left-clicking (or not)
* Fixed crash when batch-building and the project file is malformed (invalid)
* Fixed (removed) a compiler warning
* When a file's attributes change from/to read-only/read-write, it no longer requires a file reload. It also works fine now
* Read-only files no longer have this gray background color
* Fixed symbols browser UI glitch when docked in the project manager notebook
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)

delux:
There is still problem with gdb output parsing in watches window.
Example attached.

[attachment deleted by admin]

MortenMacFly:

--- Quote from: delux on May 25, 2006, 08:19:05 am ---Example attached.

--- End quote ---
...please read that: http://forums.codeblocks.org/index.php?topic=3186.0 topic. It came out of your first post. Please try what happens if you set the file encoding to UTF-8 (Settings -> Editor -> General settings -> "Default Encoding when opening files"...?!
With regards, Morten.

Edit: ...or do you mean the trailing '{' (I can see the value properly in your example)?

mandrav:

--- Quote from: delux on May 25, 2006, 08:19:05 am ---There is still problem with gdb output parsing in watches window.
Example attached.

--- End quote ---

There is no problem with gdb output parsing. There's problem with gdb's output and we can't do much about it ;)


--- Code: ---> output *ptr
{char_var = -83 'ar = 123}

--- End code ---

EDIT: Actually, it's the way gdb's output is converted to wxString. Let me look into this...

mandrav:
OK, I 've found the cause in sdk/pipedprocess.cpp. The text stream we 're reading there, is using UTF8 conversion which is clearly the problem here.
I 've updated it to use the local system encoding, which hopefully will work fine. Worked fine for me in my tests. But please test watching vars as much as possible. Test compiling too. We wouldn't want to break what already works ;)
Also, Morten, please check your test file again and tell us if it works now...

Navigation

[0] Message Index

[#] Next page