Author Topic: The 31 January 2007 build is out. (Read 36857 times)

killerbot · « **on:** January 31, 2007, 08:39:42 pm »

wxSmith:
* Added wxsItem::IsPointer to check whether given item should be represented as pointer or as object in destination classes
* wxTimer is now created as object, not pointer. This prevented memory leaks in destination classes
* Added wxsItem::GetAccessPrefix and wxsItem::GetCreatePrefix and wxsItem::Codef (Printf-like function which helped to simplify process of creating source code)
* Converted all current items to support new code-generation scheme
Added compiler settings versioning so when compiler defaults are changed the user is notified and given the chance to update to the newer settings
Compilers now save only the settings that differ from the default values. This leads to smaller configuration file
Editor syntax highlighting settings are now only saved if different than defaults
Fixed "Reset" button functionality in editor syntax highlighting page
Fixed a few problems with spaces in paths (including the resource compiler issue)

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) (is fixed with our special wx263/wx28 dll)

Belgabor · « **Reply #1 on:** January 31, 2007, 09:49:53 pm »

Quote from: killerbot on January 31, 2007, 08:39:42 pm

Added compiler settings versioning so when compiler defaults are changed the user is notified and given the chance to update to the newer settings

I'm not 100% sure, but I believe there was an error in the warning message. It said that only the advanced options are affected, which I interpreted as everything that comes up when I pressed the so-called button on the Other tab. Nevertheless Compiler logging was reset from Full command line to Task description in my case.

Quote from: killerbot on January 31, 2007, 08:39:42 pm

Fixed a few problems with spaces in paths (including the resource compiler issue)

At least for the resource complier I can confirm that. Thanks a lot

Marenz · « **Reply #2 on:** January 31, 2007, 10:30:48 pm »

Found 2 Bugs:

1)

I added to functions to a subclass, that means a class that is declared inside an other class.
e.g
class A
{
class B
{...}
}

i got class A in own headers and all classes own cpp files.
the Functions in the cpp files are write like:
returnvalue A::B::functionname(..)

now i do Rightclick -> insert all class methods without implementation.
a windows pops up, showing me every function, including the already implenented ones. I think its because its a subclass.
well second bug is
2)
in that window i choosed the 2 added functions, but it adds only one of the choosed and an other one which was not choosed.

well and maybee 3. bug, it did not write A::B::name but B::name

rev 3558

--Ano

@nthony · « **Reply #3 on:** February 01, 2007, 02:17:50 am »

Quote

Fixed a few problems with spaces in paths (including the resource compiler issue)

Mana from the heavens!! I can finally use new nightly's now!

Very very minor GUI bug:
Parts of the toolbar background do not refresh after a dialog box has been opened. I.E. after opening the "compiler & debugger" dialog and closing it, the remenants of the caption bar of the dialog was left imprimented on the background of my toolbar. This may be related to the toolbar state bug, but in any case it is very minor as it can be fixed by compiling (or any other function that updates the toolbar area).

Good work!

LCsquare · « **Reply #4 on:** February 01, 2007, 02:33:36 am »

(Sorry for my poor english)

Hi~ I am a new user of Code::Block (But already used for a few months

)

Today after I updated to this nighty build, then I restart the Code::Block, I received the following error message:

Can't read value of 'HKCR\.png\Content Type' (error 2: the system cannot find the file specified)

Then I press OK to close the error window and everything is OK (no side effect?)

Does my computer has some files missing? Please help.

stahta01 · « **Reply #5 on:** February 01, 2007, 03:09:58 am »

Quote from: LCsquare on February 01, 2007, 02:33:36 am

(Sorry for my poor english)

Hi~ I am a new user of Code::Block (But already used for a few months )

Today after I updated to this nighty build, then I restart the Code::Block, I received the following error message:

Can't read value of 'HKCR\.png\Content Type' (error 2: the system cannot find the file specified)

Then I press OK to close the error window and everything is OK (no side effect?)

Does my computer has some files missing? Please help.

Your registry has a problem; below is my best guess on how to fix it. Use a text editor and create a file called png.reg and put the below code in it. Save the file. Click on the file to import it into registry this might fix your issue but might not.
This Code is AS-IS no warranty, use with caution.

Code

REGEDIT4

[HKEY_CLASSES_ROOT\.png]
"Content Type"="image/png"
"PerceivedType"="image"

killerbot · « **Reply #6 on:** February 01, 2007, 08:02:51 am »

I wonder which component of CB or used by Cb wants to read "'HKCR\.png\Content Type' " ?

user_mv · « **Reply #7 on:** February 01, 2007, 08:15:12 am »

Greetings,

I'm a new user to the Code::Blocks IDE. I'm using Windows XP and minGW and the latest Codeblocks nightly build. I've set the global variables in Codeblocks as cb = c:\codeblocks\src and wx = c:\wxwidgets-2.6.3. I have installed wxWidgets-2.6.3 and added the latest 2.6.3 patch. The SVN version of the code I'm using is 3558.

When I load CodeBlocks.cbp and try to build it (using minGW as the compiler), it begins compiling and completes all targets up until src and then fails. It fails because the linker does not find resources.res. In fact, it appears that the resource compiler (windres) never gets called, and thus resource.res never gets built.

And BTW, there are NO spaces in the names of my directories.

To get around this problem, I manually called windres by typing

C:\codeblocks\src>windres -i "C:\codeblocks\src\src\resources\resources.rc" -J rc -o .objs\2.6\src\resources\resources.res -O coff -IC:\wxWidgets-2.6.3\include -IC:\mingw\include

and then compile again inside Codeblocks. This time the linker finds resources.res and links succefully, but I do get the warning:

Info: resolving SquirrelVM::_VM by linking to __imp___ZN10SquirrelVM3_VME (auto-import)

Is this warning normal ??

I am able to build the plugins without problems and when I run update.bat everything goes well. The newly generated Codeblocks seems to work fine. However, this temporary "fix" (assuming that's what it is) is clearly not an acceptable long term solution.

I don't know if the problem is something I'm doing wrong, or an incorrect project file (CodeBlocks.cbp), or a bug in the Codebocks code.

I hope you can fix this issue or point out what I'm missing. Thank you in advance.

stahta01 · « **Reply #8 on:** February 01, 2007, 09:02:04 am »

Quote from: killerbot on February 01, 2007, 08:02:51 am

I wonder which component of CB or used by Cb wants to read "'HKCR\.png\Content Type' " ?

I am guessing that something is trying to display an png file and it uses the registry to determine how to display it. This is complete guess work on my part. I tried to duplicate the error and could not do it by deleting the Content Type entry.

Tim S

alanwong · « **Reply #9 on:** February 01, 2007, 09:06:14 am »

Is it a bug ? When I click on a build message it don't jumps to the line.

stahta01 · « **Reply #10 on:** February 01, 2007, 09:08:43 am »

Quote from: user_mv on February 01, 2007, 08:15:12 am

Greetings,

I'm a new user to the Code::Blocks IDE. I'm using Windows XP and minGW and the latest Codeblocks nightly build. I've set the global variables in Codeblocks as cb = c:\codeblocks\src and wx = c:\wxwidgets-2.6.3. I have installed wxWidgets-2.6.3 and added the latest 2.6.3 patch. The SVN version of the code I'm using is 3558.

When I load CodeBlocks.cbp and try to build it (using minGW as the compiler), it begins compiling and completes all targets up until src and then fails. It fails because the linker does not find resources.res. In fact, it appears that the resource compiler (windres) never gets called, and thus resource.res never gets built.

And BTW, there are NO spaces in the names of my directories.

To get around this problem, I manually called windres by typing

C:\codeblocks\src>windres -i "C:\codeblocks\src\src\resources\resources.rc" -J rc -o .objs\2.6\src\resources\resources.res -O coff -IC:\wxWidgets-2.6.3\include -IC:\mingw\include

and then compile again inside Codeblocks. This time the linker finds resources.res and links succefully, but I do get the warning:

Info: resolving SquirrelVM::_VM by linking to __imp___ZN10SquirrelVM3_VME (auto-import)

Is this warning normal ??

I am able to build the plugins without problems and when I run update.bat everything goes well. The newly generated Codeblocks seems to work fine. However, this temporary "fix" (assuming that's what it is) is clearly not an acceptable long term solution.

I don't know if the problem is something I'm doing wrong, or an incorrect project file (CodeBlocks.cbp), or a bug in the Codebocks code.

I hope you can fix this issue or point out what I'm missing. Thank you in advance.

I ignore the (auto-import) warnings that I get.
But your work around using windres is NOT normal.

Tim S

stahta01 · « **Reply #11 on:** February 01, 2007, 09:12:13 am »

Quote from: alanwong on February 01, 2007, 09:06:14 am

Is it a bug ? When I click on a build message it don't jumps to the line.

Yes, it is a bug. I have no idea if it is a know bug that is being worked on. Someone complained about it in the last few days, but the C::B team member was not able to duplicate it at first. I have no idea if they could duplicate it later on.

Tim S

alanwong · « **Reply #12 on:** February 01, 2007, 09:20:48 am »

It is to be regretted that ...

once_upon_user · « **Reply #13 on:** February 01, 2007, 09:40:35 am »

Hello,

I do not give a try to every nightly built, but I enjoy having a new version compiled from SVN once for a several days.. I admire people working on this wonderful software. However There are still some improvments to made. I'm not an expert in operating CB but, When I try to use feature : "find declaration" it fails in a case
when there is a struct defined similar to the one shown below:

Code

typedef struct {
	byte bunch; 
	byte ext_num[MAX_DIR_N];
	byte int_num[MAX_DIR_NO_AB]; 
	byte opts;     
} __attribute__ ((packed))  NAME_OF_STRUCTURE;

I got result that declaration wasn't found. The problem could be with analyze last line.

stardust · « **Reply #14 on:** February 01, 2007, 10:08:43 am »

Starting C::B prints out

Quote

(codeblocks:12810): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed

and then runs.

SVN: 3557
wx2.6.1 (Linux, unicode)

BTW: Would be nice if the build/system info in Help->About could be copied/pasted and was not provided as image (label or so)...

Code::Blocks Forums

News:

Author Topic: The 31 January 2007 build is out. (Read 36857 times)

killerbot

The 31 January 2007 build is out.

Belgabor

Re: The 31 January 2007 build is out.

Marenz

Re: The 31 January 2007 build is out.

@nthony

Re: The 31 January 2007 build is out.

LCsquare

Re: The 31 January 2007 build is out.

stahta01

Re: The 31 January 2007 build is out.

killerbot

Re: The 31 January 2007 build is out.

user_mv

Re: The 31 January 2007 build is out.

stahta01

Re: The 31 January 2007 build is out.

alanwong

Re: The 31 January 2007 build is out.

stahta01

Re: The 31 January 2007 build is out.

stahta01

Re: The 31 January 2007 build is out.

alanwong

Re: The 31 January 2007 build is out.

once_upon_user

Re: The 31 January 2007 build is out.

stardust

Re: The 31 January 2007 build is out.