Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on July 21, 2007, 11:20:46 am

Title: The 20 July 2007 build (4285) is out.
Post by: killerbot on July 21, 2007, 11:20:46 am
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_wx284.7z

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

The 20 July 2007 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20070720_rev4285_win32.7z
  - Linux :
   http://prdownload.berlios.de/codeblocks/CB_20070720_rev4285_Ubuntu6.10+7.04_wx2.8.4.tar.gz (not yet)
   http://prdownload.berlios.de/codeblocks/CB_20070720_rev4285_Debian4.0_wx2.8.4.deb (not yet)
   http://prdownload.berlios.de/codeblocks/CB_20070720_rev4285_suse100-102.wx28.i586.rpm (not yet)
   http://prdownload.berlios.de/codeblocks/CB_20070720_rev4285_fc4+5.i586.rpm (not yet)


Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 20 July 2007 build (4285) is out.
Post by: rhf on July 21, 2007, 03:33:35 pm
Quote from: killerbot on July 21, 2007, 11:20:46 am
Resolved Fixed:
  • Fixed minor issues with CC tooltips
I just downloaded the 20 July nightly (4285), and it appears that the annoying tooltips display has been fixed.
Thanks very much.
Title: Re: The 20 July 2007 build (4285) is out.
Post by: marfi on July 21, 2007, 03:48:03 pm
Quote
it appears that the annoying tooltips display has been fixed

This bug is realy fixed, but CC tooltips after '.' or '->' have disapeared and aren't displayed anymore... (WinXP SP2)
Title: Re: The 20 July 2007 build (4285) is out.
Post by: dje on July 21, 2007, 04:10:24 pm
Another detail, when I right click on a method to click on Find declaration of method, the tooltip appears above the menu, hides it and makes it unclickable (see joined picture)

Dje

[attachment deleted by admin]
Title: Re: The 20 July 2007 build (4285) is out.
Post by: nenin on July 22, 2007, 05:57:39 pm
I tried to build it under Suse 10.2 - AMD64. I got error:
Code
filemanager.cpp: In function 'bool WriteWxStringToFile(wxFile&, const wxString&, wxFontEncoding, bool)':
filemanager.cpp:205: error: ambiguous overload for 'operator==' in 'buf == 0'
filemanager.cpp:205: note: candidates are: operator==(const char*, const char*) <built-in>
/usr/local/include/wx-2.8/wx/string.h:1560: note:                 bool operator==(const wxString&, const wxString&)
/usr/local/include/wx-2.8/wx/string.h:1562: note:                 bool operator==(const wxString&, const wxChar*)
/usr/local/include/wx-2.8/wx/string.h:1564: note:                 bool operator==(const wxChar*, const wxString&)
/usr/local/include/wx-2.8/wx/string.h:1607: note:                 bool operator==(const wxString&, const wxCharBuffer&)
/usr/local/include/wx-2.8/wx/string.h:1609: note:                 bool operator==(const wxCharBuffer&, const wxString&)
/usr/local/include/wx-2.8/wx/string.h:1633: note:                 bool operator==(wxChar, const wxString&) <near match>
/usr/local/include/wx-2.8/wx/string.h:1634: note:                 bool operator==(const wxString&, wxChar)
/usr/local/include/wx-2.8/wx/longlong.h:1044: note:                 bool operator==(long int, const wxLongLong&) <near match>
/usr/local/include/wx-2.8/wx/longlong.h:1057: note:                 bool operator==(long unsigned int, const wxULongLong&) <near match>
filemanager.cpp:209: error: ambiguous overload for 'operator==' in 'buf == 0'
filemanager.cpp:209: note: candidates are: operator==(const char*, const char*) <built-in>
/usr/local/include/wx-2.8/wx/string.h:1560: note:                 bool operator==(const wxString&, const wxString&)
/usr/local/include/wx-2.8/wx/string.h:1562: note:                 bool operator==(const wxString&, const wxChar*)
/usr/local/include/wx-2.8/wx/string.h:1564: note:                 bool operator==(const wxChar*, const wxString&)
/usr/local/include/wx-2.8/wx/string.h:1607: note:                 bool operator==(const wxString&, const wxCharBuffer&)
/usr/local/include/wx-2.8/wx/string.h:1609: note:                 bool operator==(const wxCharBuffer&, const wxString&)
/usr/local/include/wx-2.8/wx/string.h:1633: note:                 bool operator==(wxChar, const wxString&) <near match>
/usr/local/include/wx-2.8/wx/string.h:1634: note:                 bool operator==(const wxString&, wxChar)
/usr/local/include/wx-2.8/wx/longlong.h:1044: note:                 bool operator==(long int, const wxLongLong&) <near match>
/usr/local/include/wx-2.8/wx/longlong.h:1057: note:                 bool operator==(long unsigned int, const wxULongLong&) <near match>
Any suggestions?
gcc 4.1.2, wx 2.8.4
Title: Re: The 20 July 2007 build (4285) is out.
Post by: killerbot on July 22, 2007, 06:10:06 pm
on my suse 10.2 box (AMD 64 bit) I don't have this issue.

I wonder on how to correctly use that type, as a regular class no doc in wx.

Can it ever be 0, it seems more to be an object that exists instead of a regular pointer ???
Title: Re: The 20 July 2007 build (4285) is out.
Post by: nenin on July 22, 2007, 07:13:07 pm
Did you put any additional compiler flags when build it? I did just ./configure ./make
Title: Re: The 20 July 2007 build (4285) is out.
Post by: olipfei on July 23, 2007, 12:33:40 am
I have to confirm this compile error, on revision 4291. My system: SuSE Linux 9.1, gcc 3.3.3, wxGTK 2.8.4 ANSI on Intel 32bit. (I know, it's a bit old. But you might be happy to hear that revision 4282 is running just fine even on this older system.) Could ANSI built of wxGTK be a problem?? Configuration of C::B: ./configure --prefix=/usr --enable-contrib ; make.
Title: Re: The 20 July 2007 build (4285) is out.
Post by: Biplab on July 23, 2007, 06:19:49 am
Quote from: killerbot on July 22, 2007, 06:10:06 pm
on my suse 10.2 box (AMD 64 bit) I don't have this issue.

I wonder on how to correctly use that type, as a regular class no doc in wx.

Can it ever be 0, it seems more to be an object that exists instead of a regular pointer ???

I'm also confused with this issue.  :(

But it may be 0 as, AFAIK, wxString::mb_str() returns a NULL string if it fails. :)

Quote from: olipfei on July 23, 2007, 12:33:40 am
I have to confirm this compile error, on revision 4291. My system: SuSE Linux 9.1, gcc 3.3.3, wxGTK 2.8.4 ANSI on Intel 32bit. (I know, it's a bit old. But you might be happy to hear that revision 4282 is running just fine even on this older system.) Could ANSI built of wxGTK be a problem?? Configuration of C::B: ./configure --prefix=/usr --enable-contrib ; make.

It appears that on certain build configurations of wx, wxCharBuffer::== is undefined. I've fixed this issue in Rev 4293. Please check out & compile the latest revision and post your feedback. :)
Title: Re: The 20 July 2007 build (4285) is out.
Post by: nenin on July 23, 2007, 03:39:21 pm
I compilled corrected version, but it can not save files.  :cry:


[attachment deleted by admin]