News:

The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .

Main Menu

The 22 May 2006 build is out.

Started by killerbot, May 22, 2006, 08:23:11 PM

Previous topic - Next topic

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 22 May 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_20060522_rev2484_win32.7z
  - Linux :
         http://download.berlios.de/codeblocks/CB_20060522_rev2484.deb
         http://download.berlios.de/codeblocks/CB_20060522_rev2484_fc4+5.rpm

Resolved Fixed:


  • Changed the pool's condition lifetime
  • Restored optimisations that were accidentially reverted in 2472
  • Replaced the condition with a semaphore (just like the previous implementation)
  • wxSmith Redesign :
    wxFlexGridSizer,wxGridSizer
    - Constructor Code parameters should be row,col,vgap,hgap instead of col,row,vgap,hgap

    - Small modification of code to keep the consistency of coding

    wxCalendarctrl
    - Code generated wrong for wxDateTime

    wxDatePickerCtrl
    - - Small modification of code to keep the consistency of coding
  • Fixed message manager auto-hiding to respect the user settings in environment options
  • Exposed "Info" (normal) type for compiler regexes in advanced compiler options
  • Added project/target header in build messages (updated whenever the currently compiling project/target changes)
  • Cleaned up some logging code in compiler plugin
  • added project wizard (new format) for a GLFW application
  • added project wizard (new format) for a GLUT application
  • updated Code::Blocks project files to include GLFW and GLUT files

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)


asdf

You know what would be great...

Since you are redesigning wxSmith anyways, how about a way to manually place components... Without using sizers...

thomas

Just to be sure, you do know how wxWidgets dialog layout works?
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

tretton

Beeeautiful! The auto-show feature is so sweet! =)

riverbird

I don't know what I aught to do? my rc2 can run well,but my night can't run,I don't know the reason.

dronT78

please make a linux rpm package :roll:
thank you

takeshimiya

Quote from: asdf on May 22, 2006, 10:29:13 PM
Since you are redesigning wxSmith anyways, how about a way to manually place components... Without using sizers...

Quote from: byo on February 15, 2006, 10:57:45 PM
You can put buttons anywhere You like, just remove main sizer in window and put Your buttons right into it.
Currently wxSmith doesn't support this mode well (there's no snap to grid etc), and the main problem maybe that currently window size can not be changed in editor. But You can try :)

I promise that after reaching required level of stabilityin wxSmith I'll work on this :)

delux

#7
I suspect many users are aware of incorrect presentation of watches while debugging (gcc).
Looks like output from gdb is misparsed - watches window, local variables / function arguments.
I think that when it comes to watching char typed variables (and struct members) gdb output contains the ascii character corresponding to var's value and C::B has trouble parsing such string.

(EDIT)
for now I use "set output-radix 16" gdb initialization command to force more clean gdb output for "info locals" and such.

MortenMacFly

Quote from: delux on May 23, 2006, 07:34:34 AM
I suspect many users are aware of incorrect presentation of watches while debugging (gcc).
Please post an example if you want this to be fixed.
Is it possible to strip down such a "mis-parsing" into a single file as an example? And give us an explanation where to set the breakpoints and what to watch... That would help a lot!
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

TheTuxKeeper

Quote from: dronT78 on May 23, 2006, 06:29:23 AM
please make a linux rpm package :roll:
thank you
Uploaded, but not yet downloadable (has to be added to the project files by killerbot first) ;)
Nightly builds for openSUSE

killerbot


killerbot

Quote from: riverbird on May 23, 2006, 05:40:11 AM
I don't know what I aught to do? my rc2 can run well,but my night can't run,I don't know the reason.
Can you tell us step by step what you did, and what exaclty goes wrong (also tell us your OS).

TheTuxKeeper

Nightly builds for openSUSE

delux

regarding gdb parsing I attach an example;

[attachment deleted by admin]

dronT78

Quote
Quote
done
Wow, quick service as always
thanks boss!  8)