Code::Blocks

User forums => Nightly builds => Topic started by: killerbot on August 02, 2008, 09:48:45 pm

Title: The 02 August 2008 build (5177) is out.
Post by: killerbot on August 02, 2008, 09:48:45 pm
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works (http://forums.codeblocks.org/index.php/topic,3232.0.html).

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx288.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc421.7z

The 02 August 2008 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20080802_rev5177_win32.7z
  - Linux :
   none

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 02 August 2008 build (5177) is out.
Post by: L_O_J on August 03, 2008, 04:18:52 am
This might be a bug...
Since the July 22 build everytime I try to use Ctrl + Delete, it doesn't delete the word, instead searching for it  :shock:. Is it a new behaviour or what ? Since I use Ctrl + Delete a lot, it's pretty hard to change habit :D
Title: Re: The 02 August 2008 build (5177) is out.
Post by: killerbot on August 03, 2008, 10:43:37 am
this seems to be a bug of wxwidgets --> ctrl + .   ; but ./del is the same physical key :-(

workaround : choose different binding for the ctrl+ .
Title: Re: The 02 August 2008 build (5177) is out.
Post by: berte on August 03, 2008, 10:51:26 am
hello everbody,

thanks for new version but internationalization problem still continuing.

(http://img155.imageshack.us/img155/7365/bugsim0.th.jpg) (http://img155.imageshack.us/my.php?image=bugsim0.jpg)
Title: Re: The 02 August 2008 build (5177) is out.
Post by: killerbot on August 03, 2008, 11:49:35 am
hello everbody,

thanks for new version but internationalization problem still continuing.

(http://img155.imageshack.us/img155/7365/bugsim0.th.jpg) (http://img155.imageshack.us/my.php?image=bugsim0.jpg)

Could you file this as a bug report please at berlios ??
Title: Re: The 02 August 2008 build (5177) is out.
Post by: berte on August 03, 2008, 01:40:13 pm
Yes killerbot, I reported this bug long long time ago.
It's not important native users but it's not a good look :-)

cheers.
Title: Re: The 02 August 2008 build (5177) is out.
Post by: jens on August 03, 2008, 02:28:19 pm
I just uploaded svn r5177 to my server (http://apt.jenslody.de/).

Important notice (please read carefully):
I changed the package- and directory-structure of my Code::Blocks build to make it more debian-compliant.
I also split off the architecture-independent files from the codeblocks-package and put them into codeblocks-common.
The architecture-dependent libraries, that are parts of the contrib-plugins are now in "/usr/lib/codeblocks" and only the architecture-independent parts remain in "/usr/share/codeblocks".
The changes are based on a patch provided by "daniel2000".
More details can be found here (http://forums.codeblocks.org/index.php/topic,8755.msg63619.html#msg63619).
I posted a patch in this thread. I modified this patch for the actual nightly, to make lintian run without errors.

If you get any errors caused by this changes, please send me a PN or a mail.
I will be out for work the next week (most times without internet), except for the wednesday.
So I can look for mails from time to time from late tuesday to early thursday.

The changes work for me without any problems, so I hope they will also do it for other users.

Please have in mind, that these changes are not part of the official svn-code, so if anything does not work due to the changes, don't blame C::B.
Title: Re: The 02 August 2008 build (5177) is out.
Post by: Loaden on August 04, 2008, 04:30:47 pm
Please look 'Screenshot.png' first:
in 1: the default encoding is 'Windows 936',
in 2: createdb.cpp include some chinese char, when i open it use CB,
in 3: CB open it use ISO-8895-1, so, i can't show chinese char.

payout.cpp include chinese char also. but it's can opened by CB to use 'Windows 936'.

Why two files include the same chinese code, but it opened use 'Default encoding', it's auto changed to 'ISO-8895-1'.

I need help, because i am a china developer, i can't use chinese to program, it's made my headache.

Thanks! please fix this bug.

[attachment deleted by admin]
Title: Re: The 02 August 2008 build (5177) is out.
Post by: Biplab on August 04, 2008, 05:25:54 pm
Please look 'Screenshot.png' first:
in 1: the default encoding is 'Windows 936',
in 2: createdb.cpp include some chinese char, when i open it use CB,
in 3: CB open it use ISO-8895-1, so, i can't show chinese char.

Save your file in UTF-8 encoding. C::B can't detect Windows 936 encoding and it sets a fallback encoding for it.
Title: Re: The 02 August 2008 build (5177) is out.
Post by: Acki on August 05, 2008, 01:26:13 am
still the double click problem !!!  :?  :(
Title: Re: The 02 August 2008 build (5177) is out.
Post by: Loaden on August 05, 2008, 05:37:40 am
Please look 'Screenshot.png' first:
in 1: the default encoding is 'Windows 936',
in 2: createdb.cpp include some chinese char, when i open it use CB,
in 3: CB open it use ISO-8895-1, so, i can't show chinese char.

Save your file in UTF-8 encoding. C::B can't detect Windows 936 encoding and it sets a fallback encoding for it.
It's can't compile use VC2003, because VC2003 can't support UTF-8 format.
But my project must support cross platform. In Linux, use GCC, and use VC2003 under Windows.
I muse use Windows 936 encoding to support chinese code.

and in windows OS, set default encoding to Windows 936, it work fine!
this problem only appear in linux.
Title: Re: The 02 August 2008 build (5177) is out.
Post by: Etienne on August 05, 2008, 10:01:37 am
Hello,

Thanks to continue making nightly builds!

I have two bug:

- This one started after the 5106svn version, when double clicking on a workspace, its tells a file is missing  (please see attached file)...(even with every plugin disabled), ( its works with cb5106)

- This one was from 5106svn to now, I can't say when its started: sometime CB show it is in Debug mode, but compile in Release, and so on ; a workaround is to change Debug/Release mode, twice, in the menu to set it correctly...

Thanks for all.

See you

Etienne de Foras


[attachment deleted by admin]
Title: Re: The 02 August 2008 build (5177) is out.
Post by: Loaden on August 05, 2008, 10:52:26 am
Hello,

Thanks to continue making nightly builds!

I have two bug:

- This one started after the 5106svn version, when double clicking on a workspace, its tells a file is missing  (please see attached file)...(even with every plugin disabled), ( its works with cb5106)

- This one was from 5106svn to now, I can't say when its started: sometime CB show it is in Debug mode, but compile in Release, and so on ; a workaround is to change Debug/Release mode, twice, in the menu to set it correctly...

Thanks for all.

See you

Etienne de Foras


I find this problem too.
Title: Re: The 02 August 2008 build (5177) is out.
Post by: thomas on August 05, 2008, 11:20:21 am
It's can't compile use VC2003, because VC2003 can't support UTF-8 format.
Well, use UTF-16 instead then.
Title: Re: The 02 August 2008 build (5177) is out.
Post by: Loaden on August 06, 2008, 03:37:53 am
It's can't compile use VC2003, because VC2003 can't support UTF-8 format.
Well, use UTF-16 instead then.

If i select UTF16-LE, i can't use _T() or _(). example:
Code: [Select]
wxButton* pShow = new wxButton(this, ID_BTN_SHOW, _T("开始"));or:
Code: [Select]
wxButton* pShow = new wxButton(this, ID_BTN_SHOW, _("开始"));show error info when compile:
Code: [Select]
src\main.cpp|23|error C2001: newline in constant|
src\main.cpp|23|fatal error C1057: unexpected end of file in macro expansion|
||=== Build finished: 2 errors, 0 warnings ===|

but if i changed this code to:
Code: [Select]
wxButton* pShow = new wxButton(this, ID_BTN_SHOW, L"开始");it's compile success.

how to use _T() or _() ?
Title: Re: The 02 August 2008 build (5177) is out.
Post by: Loaden on August 06, 2008, 04:00:33 am
Why not write BOM into file? include UTF-8, UTF-16...?

example, UTF-8's BOM is 'EF BB BF', but when i set default encoding to 'UTF-8', and add some file use CB, it's can't insert BOM at the file first.

UTF-16LE's BOM is 'FF FE', and UTF-16BE's BOM is 'FE FF'?

I hope CB add BOM into file. thanks!
Title: Re: The 02 August 2008 build (5177) is out.
Post by: Acki on August 06, 2008, 12:21:12 pm
- This one started after the 5106svn version, when double clicking on a workspace, its tells a file is missing  (please see attached file)...(even with every plugin disabled), ( its works with cb5106)
I find this problem too.
well, I'm reporting this since release 5142 with no response... :cry:
I hope they don't ignore us !!!  :lol:
Title: Re: The 02 August 2008 build (5177) is out.
Post by: Biplab on August 06, 2008, 04:56:09 pm
Why not write BOM into file? include UTF-8, UTF-16...?

example, UTF-8's BOM is 'EF BB BF', but when i set default encoding to 'UTF-8', and add some file use CB, it's can't insert BOM at the file first.

UTF-16LE's BOM is 'FF FE', and UTF-16BE's BOM is 'FE FF'?

I hope CB add BOM into file. thanks!

Have you tried Edit > File encoding > Save byte-order-mark (BOM) option?? C::B is not as dumb as you think.
Title: Re: The 02 August 2008 build (5177) is out.
Post by: Loaden on August 07, 2008, 05:04:02 am
Have you tried Edit > File encoding > Save byte-order-mark (BOM) option?? C::B is not as dumb as you think.
Thanks!

But itt's can't auto complete.
Have some settings set this option to default enable?

If i have a project, and the project include many files with 'Windows 936' encoding. now i want convert to 'UTF-8' and with BOM write, now, i can do it only one by one.

I hope CB have a option: if save or create a file, it's can auto write BOM.
Title: Re: The 02 August 2008 build (5177) is out.
Post by: indigo0086 on August 08, 2008, 02:53:21 pm
I was wondering, in the "Insert all class methods without implementation.  Is it possible to
1) remove the comments added
2) make the definition order the same as they are ordered in the class declaration.