Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on February 16, 2006, 11:04:34 pm

Title: The 16 february 2006 build is out.
Post by: killerbot on February 16, 2006, 11:04:34 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.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 for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26_gcc_cb.7z

The 16 February 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_20060216_rev2016_win32.7z
  - Linux : not supported yet


Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 16 february 2006 build is out.
Post by: jimshen on February 17, 2006, 01:49:09 am
There is still a problem. I use chinese characters in my program. Those lines that contain chinese characters were deleted automatically when I used source code formatter (AStyle).
Title: Re: The 16 february 2006 build is out.
Post by: sethjackson on February 17, 2006, 01:51:43 am
Quote from: jimshen on February 17, 2006, 01:49:09 am
There is still a problem. I use chinese characters in my program. Those lines that contain chinese characters were deleted automatically when I used source code formatter (AStyle).

Maybe this is a AStyle problem not a C::B problem????
Title: Re: The 16 february 2006 build is out.
Post by: Conan Kudo on February 17, 2006, 03:01:35 am
Quote
Regressions/Confirmed/Annoying/Common bugs:

  • DDE bug : clicking in windows explorer on a CB registered file throws an error message box
  • toolbar-images-not-changing-state (is a wx problem)

what does it mean by an error message box? file associations work fine for me...
Title: Re: The 16 february 2006 build is out.
Post by: jimshen on February 17, 2006, 03:53:13 am
Quote from: sethjackson on February 17, 2006, 01:51:43 am
Maybe this is a AStyle problem not a C::B problem????

Not exactlly. I download AStyle from SourceForge (not CVS), and It works well. So I think that the problem is in plugin.

The attachment is c source file I used to test.



[attachment deleted by admin]
Title: Re: The 16 february 2006 build is out.
Post by: jayatk on February 17, 2006, 04:48:50 am
Quote from: killerbot on February 16, 2006, 11:04:34 pm
added support for basic GNU ARM compiler (adjusted patch : 1424406)


Yeah!
 :D :D
Title: Re: The 16 february 2006 build is out.
Post by: killerbot on February 17, 2006, 07:27:16 am
Quote from: Pharaoh Atem on February 17, 2006, 03:01:35 am
Quote
Regressions/Confirmed/Annoying/Common bugs:

  • DDE bug : clicking in windows explorer on a CB registered file throws an error message box
  • toolbar-images-not-changing-state (is a wx problem)

what does it mean by an error message box? file associations work fine for me...

Sometimes, really sometimes, though sometimes it can be more then sometimes ;-) when you double click on a cbp registered file, a message box pops up saying the file could not be found, but in the end it does open in CB. It's very weird.
Title: Re: The 16 february 2006 build is out.
Post by: Conan Kudo on February 17, 2006, 01:33:56 pm
That is strange.... Thankfully that has never happened to me...
What about the toolbar-images-not-changing-state thing, what does it mean by wx problem
If it is talking about hover over mouse and it does not change, well it changes.... Like it is supposed to...
Title: Re: The 16 february 2006 build is out.
Post by: takeshimiya on February 17, 2006, 03:23:00 pm
Quote from: Pharaoh Atem on February 17, 2006, 01:33:56 pm
That is strange.... Thankfully that has never happened to me...
What about the toolbar-images-not-changing-state thing, what does it mean by wx problem
If it is talking about hover over mouse and it does not change, well it changes.... Like it is supposed to...

No, it happens for example in the Stop button of the Debugger's toolbar. It is always red, where it should be grayed out when there is no debugging session. Sometimes happens for others buttons, like Search.
It only happens on Windows though.

Anyone with wx2.6.3RC1 checked if the bug it's still there?
Title: Re: The 16 february 2006 build is out.
Post by: Michael on February 17, 2006, 03:31:55 pm
Quote from: Takeshi Miya on February 17, 2006, 03:23:00 pm
It only happens on Windows though.

 :(

Quote from: Takeshi Miya on February 17, 2006, 03:23:00 pm
Anyone with wx2.6.3RC1 checked if the bug it's still there?

The bug is still there :(. And there is another one too with toolbar (or it seems so). Look at here (http://forums.codeblocks.org/index.php?topic=2331.0).

Best wishes,
Michael
Title: Re: The 16 february 2006 build is out.
Post by: mandrav on February 17, 2006, 03:32:47 pm
Quote from: Takeshi Miya on February 17, 2006, 03:23:00 pm
No, it happens for example in the Stop button of the Debugger's toolbar. It is always red, where it should be grayed out when there is no debugging session. Sometimes happens for others buttons, like Search.
It only happens on Windows though.

What's even more strange, is that the compiler's Stop button uses the exact same image file but it works just fine...
Title: Re: The 16 february 2006 build is out.
Post by: Michael on February 17, 2006, 03:34:30 pm
Quote from: mandrav on February 17, 2006, 03:32:47 pm
Quote from: Takeshi Miya on February 17, 2006, 03:23:00 pm
No, it happens for example in the Stop button of the Debugger's toolbar. It is always red, where it should be grayed out when there is no debugging session. Sometimes happens for others buttons, like Search.
It only happens on Windows though.

What's even more strange, is that the compiler's Stop button uses the exact same image file but it works just fine...

Yes, I have remarked the same thing. I just wonder why...

Best wishes,
Michael
Title: Re: The 16 february 2006 build is out.
Post by: takeshimiya on February 17, 2006, 03:35:47 pm
Quote from: Michael on February 17, 2006, 03:31:55 pm
The bug is still there :(. And there is another one too with toolbar (or it seems so).

That's probably wxAUI. Can you check it if it happens with wxAUI project example?
If yes, please notify the author here: http://www.kirix.com/en/community/forums/viewforum.php?f=15
If not, probably it's because the toolbars are XRC, and toolbars loaded from XRC could be buggy (hey, the XRC system is new in wxWidgets after all).