Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on February 01, 2006, 10:54:22 pm

Title: The 01 february 2006 build is out.
Post by: killerbot on February 01, 2006, 10:54:22 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 01 February 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_01feb2006_rev1916_win32.7z
  - Linux : not supported yet


Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 01 february 2006 build is out.
Post by: artoj on February 02, 2006, 10:24:37 am
@killerbot:

I'm unable to reproduce the DDE bug, maybe it should be removed from the red list?

Another thing: what settings are you using to compress the 7z archives. Currently today's build is about 3,20 MB. Using the Maximum setting in 7-zip I was able to compress it to 3,04 MB. By using the Ultra setting the archive's size was down to 2,88 MB.
Title: Re: The 01 february 2006 build is out.
Post by: killerbot on February 02, 2006, 11:41:04 am
I use normal, ok will switch to ultra this evening (if I remember) ;-)
Title: Re: The 01 february 2006 build is out.
Post by: Michael on February 02, 2006, 12:10:18 pm
I use normal, ok will switch to ultra this evening (if I remember) ;-)

You can also try to tune the different parameters depending on your computer's resources to get a better compression rate (if this still allow later the users to decompress it... :)).

Michael
Title: Re: The 01 february 2006 build is out.
Post by: Szabadember on February 02, 2006, 03:29:35 pm
Don't you report ALL bug fixes in the changelog?
I found some bugs in earlier builds (jan xx), but they disappeared without being reported in the changelog...
(Codeblocks crashes while dragging a docked window)
Title: Re: The 01 february 2006 build is out.
Post by: killerbot on February 02, 2006, 03:35:53 pm
the thing is, we don't work 100% correctly. I think we should adopt to (for better tracking) :

- for every bug, problem : bug report @ SF

Then I can much easier refer to those things, now I use the commit comments from the devs. So when they fix something, for which there's no bugreport it's hard to know unless they state it explicitly. But sometimes during one commit several small issues are fixed, but no full list.

Well at the speed things still change today, it is maybe a little bit hard to keep such a 'close' track. Certainly something to do in the future.

[edit] about the docking, another dock mechanism is in use, so maybe your previous build was before that one. The old docking mechanism had several drawback and limitation, the new one is way better. So changes are ....
Title: Re: The 01 february 2006 build is out.
Post by: Michael on February 02, 2006, 03:37:45 pm
(Codeblocks crashes while dragging a docked window)
[/quote]

Could you explain a bit more this point :?? I can drag windows without any problems.

Michael
Title: Re: The 01 february 2006 build is out.
Post by: Szabadember on February 02, 2006, 04:47:30 pm
That docking problem was already fixed...

I found a bug in the source code formatter(if this is a bug...):
It can't format Resource scripts, if i use begin/end instead of {/}.

All other source code formatter bugs are gone... (i couldn't reproduce any else)

It would be nice, if the source code formatter would format the code after pushing the RETURN/ENTER key,
not the whole file, only those parts that need to be reformatted...

The Code Completion plugin works strange or i have misunderstanded it...
My definition of a Code Completion plugin would be:
Showing a list of matching function names after typing at least 4 charachters. (Function names from headers, classes, etc...)
Showing arguments for the function after typing a '(' after a valid function name
Showing the members of a class after writing a '.' after a valid class variable.
Title: Re: The 01 february 2006 build is out.
Post by: Michael on February 02, 2006, 05:21:38 pm
That docking problem was already fixed...

Ah ok, I have misunderstood.

I found a bug in the source code formatter(if this is a bug...):
It can't format Resource scripts, if i use begin/end instead of {/}.

Could you may be post the bug at SF?

It would be nice, if the source code formatter would format the code after pushing the RETURN/ENTER key,
not the whole file, only those parts that need to be reformatted...

You can post a feature request at SF :).

The Code Completion plugin works strange or i have misunderstanded it...
My definition of a Code Completion plugin would be:
Showing a list of matching function names after typing at least 4 charachters. (Function names from headers, classes, etc...)
Showing arguments for the function after typing a '(' after a valid function name
Showing the members of a class after writing a '.' after a valid class variable.

The code completion is WIP. If you find bugs post them to SF. If you would like new features post them too to SF :).

Michael
Title: Re: The 01 february 2006 build is out.
Post by: Ceniza on February 02, 2006, 05:34:02 pm
Since the source formatter plugin relies on AStyle, the AStyle specific bugs should be posted in AStyle's project site @ SourceForge.