News:

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

Main Menu

The 09 July 2006 build is out.

Started by killerbot, July 09, 2006, 10:53:28 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_wx2.6.3p2.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 (2.6.2) for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26_gcc_cb.7z

The 09 July 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_20060709_rev2719_win32.7z
  - Linux :
         http://download.berlios.de/codeblocks/CB_20060709_rev2719_Ubuntu6.06.deb (not this time)
         http://download.berlios.de/codeblocks/CB_20060709_rev2719_fc4+5.rpm


Resolved Fixed:


  • Changed resource loading in all contrib plugins to new preloading scheme
  • envvars plugin: fixed wrong call to OnAttach() (Thanks Thomas)

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)
  • menu items with icon not correctly aligned (since wx263)


walker

a shortcut key problem

Alt + F, S should stop at "Save", not "Save all files"

orefa

Yes, not only this one but all menu shortcuts are funky. Try 'C' to close and see what happens. This problem was identified a while back and a bug report has already been issued on this.

zhangxingcun

I am not sure .Maybe my computer is wrong!
I use XP-sp2
  wxWidgets-2.6.3
  MinGW5.0.3 installtype is candidate

when I compile

:: === Code::Blocks, scintilla ===

C:\wxWidgets-2.6.3\include\wx\dnd.h:53: warning: inline function `bool wxIsDragResultOk(wxDragResult)' declared as dllimport: attribute ignored
C:\wxWidgets-2.6.3\include\wx\dnd.h:53: warning: inline function `bool wxIsDragResultOk(wxDragResult)' declared as dllimport: attribute ignored
C:\wxWidgets-2.6.3\include\wx\dnd.h:53: warning: inline function `bool wxIsDragResultOk(wxDragResult)' declared as dllimport: attribute ignored
:: === Code::Blocks, wxFlatNotebook ===
C:\wxWidgets-2.6.3\include\wx\dnd.h:53: warning: inline function `bool wxIsDragResultOk(wxDragResult)' declared as dllimport: attribute ignored
:: === Code::Blocks, sdk ===
C:\wxWidgets-2.6.3\include\wx\dnd.h:53: warning: inline function `bool wxIsDragResultOk(wxDragResult)' declared as dllimport: attribute ignored
:: === Code::Blocks, src ===
C:\wxWidgets-2.6.3\include\wx\dnd.h:53: warning: inline function `bool wxIsDragResultOk(wxDragResult)' declared as dllimport: attribute ignored
:: === Code::Blocks, Code-completion ===
C:\wxWidgets-2.6.3\include\wx\dnd.h:53: warning: inline function `bool wxIsDragResultOk(wxDragResult)' declared as dllimport: attribute ignored
:: === Build finished: 0 errors, 7 warnings ===

Mr. Awesome

Just installed this build over my last one from a few months ago, and when I open CB I get the following error:

The procedure entry point _ZNK7wRegEx7MatchesEPKwij could not be located in the dynamic link library wxmsw26u_gcc_cb.dll.

WinXP SP-2

Jewe

Quote from: Mr. Awesome on July 10, 2006, 09:32:15 AM
Just installed this build over my last one from a few months ago, and when I open CB I get the following error:

The procedure entry point _ZNK7wRegEx7MatchesEPKwij could not be located in the dynamic link library wxmsw26u_gcc_cb.dll.

WinXP SP-2
Did you also install the latest wxwidgets dll?
Anything curved in the hardware can be straighten with software :D
OS: Vista64 + Debian(to play with)
Compiler: mingw IDE: Code::Blocks Nightly WX: 2.8.0

Jewe

wxsmith wizard does not understand ok.

reproduction:
1. start c::B
2. new project
3. wxsmith
4. set the config. (any config)
5. press ok.. you can press ok and ok and ok and ok..
Anything curved in the hardware can be straighten with software :D
OS: Vista64 + Debian(to play with)
Compiler: mingw IDE: Code::Blocks Nightly WX: 2.8.0

thomas

Quote from: zhangxingcun on July 10, 2006, 09:23:41 AM...
Ignore them. These are normal wxWidgets warnings.


Quote from: Mr. Awesome on July 10, 2006, 09:32:15 AMThe procedure entry point _ZNK7wRegEx7MatchesEPKwij could not be located in the dynamic link library wxmsw26u_gcc_cb.dll.
The error pretty much tells you what you need to do
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Jewe

find and replace is not working as expected.

reproduction:
1. take a copy of a source file
2. make the copy read only.
3. open it in C::B without a project.
4. find and replace some text.

result: no text has been changed and no warning/reason why not.

using:
XP sp2 and this build.
Anything curved in the hardware can be straighten with software :D
OS: Vista64 + Debian(to play with)
Compiler: mingw IDE: Code::Blocks Nightly WX: 2.8.0

sethjackson

Quote from: Jewe on July 10, 2006, 11:17:20 AM
find and replace is not working as expected.

reproduction:
1. take a copy of a source file
2. make the copy read only.
3. open it in C::B without a project.
4. find and replace some text.

result: no text has been changed and no warning/reason why not.

using:
XP sp2 and this build.

You knowingly opened a read-only file, and you want C::B to tell you that you did so when you try to "edit" (search, and replace) in it?  :shock:

Jewe

Quote from: sethjackson on July 10, 2006, 02:23:46 PM
You knowingly opened a read-only file, and you want C::B to tell you that you did so when you try to "edit" (search, and replace) in it?  :shock:

What do you think.? 
I had to figure out that they were read only because my file editor did not tell me.
and even so, it should still work and because it a defect I wrote a 1,2,3 reproduction report.
So that the nice people of C::B can fix the problem without having to figure out how to reproduce the problem.

any problems with that.?
Anything curved in the hardware can be straighten with software :D
OS: Vista64 + Debian(to play with)
Compiler: mingw IDE: Code::Blocks Nightly WX: 2.8.0

PsYhLo

What about the SDL project template
i'm new to sdl so it will be nice to put this template :)

tnx in advance
[url="http://img529.imageshack.us/img529/822/3664286vy.png"]http://img529.imageshack.us/img529/822/3664286vy.png[/url]

byo

Quote from: Jewe on July 10, 2006, 10:07:21 AM
wxsmith wizard does not understand ok.

reproduction:
1. start c::B
2. new project
3. wxsmith
4. set the config. (any config)
5. press ok.. you can press ok and ok and ok and ok..

Do you mean that wizard window does not close at all? It should close right after new project is created.

thomas

QuoteI had to figure out that they were read only because my file editor did not tell me.
Code::Blocks used to tell you that a file was read-only by showing it with a grey background. This was (much to my disapproval) removed without any replacement due to repeated demand from our community. Personally, I liked it a lot better with a greyed background, as it was much clearer what was going on. Anyway, it is as it is now.

As a visible hint, the project manager shows a little "lock" icon on project files that are read-only, and a "broken file" icon on project files that are missing. Since having files organised in a project is the normal case, this is usually not a restriction.
If you don't have a project open, then of course it is a bit hard to determine that a file is read-only, granted.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

mandrav

Quote from: thomas on July 10, 2006, 04:30:12 PM
Code::Blocks used to tell you that a file was read-only by showing it with a grey background. This was (much to my disapproval) removed without any replacement due to repeated demand from our community. Personally, I liked it a lot better with a greyed background, as it was much clearer what was going on. Anyway, it is as it is now.

As a visible hint, the project manager shows a little "lock" icon on project files that are read-only, and a "broken file" icon on project files that are missing. Since having files organised in a project is the normal case, this is usually not a restriction.
If you don't have a project open, then of course it is a bit hard to determine that a file is read-only, granted.

I don't get it. What's wrong with the "Read-only" indicator in the right side of the status bar?
Be patient!
This bug will be fixed soon...