Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on July 09, 2006, 10:53:28 pm

Title: The 09 July 2006 build is out.
Post by: killerbot on July 09, 2006, 10:53:28 pm
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:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 09 July 2006 build is out.
Post by: walker on July 10, 2006, 04:40:02 am
a shortcut key problem

Alt + F, S should stop at "Save", not "Save all files"
Title: Re: The 09 July 2006 build is out.
Post by: orefa on July 10, 2006, 05:00:29 am
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.
Title: Re: The 09 July 2006 build is out.
Post by: zhangxingcun on July 10, 2006, 09:23:41 am
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 ===
Title: Re: The 09 July 2006 build is out.
Post by: 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
Title: Re: The 09 July 2006 build is out.
Post by: Jewe on July 10, 2006, 10:05:35 am
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?
Title: Re: The 09 July 2006 build is out.
Post by: 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..
Title: Re: The 09 July 2006 build is out.
Post by: thomas on July 10, 2006, 10:12:11 am
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 am
The 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
Title: Re: The 09 July 2006 build is out.
Post by: 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.
Title: Re: The 09 July 2006 build is out.
Post by: sethjackson on July 10, 2006, 02:23:46 pm
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:
Title: Re: The 09 July 2006 build is out.
Post by: Jewe on July 10, 2006, 03:01:47 pm
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.?
Title: Re: The 09 July 2006 build is out.
Post by: PsYhLo on July 10, 2006, 03:48:15 pm
What about the SDL project template
i'm new to sdl so it will be nice to put this template :)

tnx in advance
Title: Re: The 09 July 2006 build is out.
Post by: byo on July 10, 2006, 04:25:37 pm
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.
Title: Re: The 09 July 2006 build is out.
Post by: thomas on July 10, 2006, 04:30:12 pm
Quote
I 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.
Title: Re: The 09 July 2006 build is out.
Post by: mandrav on July 10, 2006, 04:55:46 pm
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?
Title: Re: The 09 July 2006 build is out.
Post by: orefa on July 10, 2006, 05:12:02 pm
I never even noticed that the status bar showed "read only" for these files. This is not where I look when I edit code. The status bar can also be turned off and some users surely have it this way. So if your project is not expanded or if you work with a single file then no hint is shown at all.

Like Thomas, I also liked the gray background for read-only files. There was no possible misinterpretation then. Maybe this should be a check box option initially set by default for safety, but one that users can turn off.
Title: Re: The 09 July 2006 build is out.
Post by: thomas on July 10, 2006, 05:36:55 pm
Nothing is wrong with it, except if you use Code::Blocks as a no-project-text-editor.
In that case, it fails miserably, as there is no visual clue whatsoever.
(EDIT: Oh, you mean the bottom right corner... :))

I thought it might help to display a (R) in the title tab, but that turns out to be a real pain...

EDIT:
Quote
I never even noticed that the status bar showed "read only" for these files.
Huh...? What...? I never saw that either ;)
Title: Re: The 09 July 2006 build is out.
Post by: Game_Ender on July 10, 2006, 05:55:56 pm
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:

Here is what Xcode does:  If I open a read only file the little icon in the title bar that indicates file type has a padlock in the lower left corner.  The status bar in the Code::Blocks serves a similar purpose.  Now if I do any action that would make a change to the file a message box pops up and asks me if I wish to continue, telling me that I will only be able to save a copy of the file if I edit it. 

I do think that is better than failing silently.
Title: Re: The 09 July 2006 build is out.
Post by: mandrav on July 10, 2006, 05:58:22 pm
Quote from: orefa on July 10, 2006, 05:12:02 pm
I never even noticed that the status bar showed "read only" for these files. This is not where I look when I edit code.

Although my reply was directed to Thomas, I 'll tell you that neither do I look there when I edit code. But I do look there when I want to check the editor's status...

Also I 'm not questioning this specific request's grounds. I just pointed out that while the gray background is gone, there is another indicator in place.
Title: Re: The 09 July 2006 build is out.
Post by: takeshimiya on July 11, 2006, 05:18:56 am
Quote from: Game_Ender on July 10, 2006, 05:55:56 pm
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:

Here is what Xcode does:  If I open a read only file the little icon in the title bar that indicates file type has a padlock in the lower left corner.  The status bar in the Code::Blocks serves a similar purpose.  Now if I do any action that would make a change to the file a message box pops up and asks me if I wish to continue, telling me that I will only be able to save a copy of the file if I edit it. 

I do think that is better than failing silently.

I think that's the best solution. :)
Title: Re: The 09 July 2006 build is out.
Post by: sethjackson on July 11, 2006, 02:40:24 pm
Quote from: Jewe on July 10, 2006, 03:01:47 pm
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.?

Oh sorry my bad. I thought you knew the file was read-only...... Sorry my fault.
Title: Re: The 09 July 2006 build is out.
Post by: Jewe on July 14, 2006, 08:52:18 am
Quote from: byo on July 10, 2006, 04:25:37 pm
Do you mean that wizard window does not close at all? It should close right after new project is created.

Yes thats what I mean.
Sorry for the late responce.
I was out of the office for a couple of days.