User forums > Nightly builds

The 01 february 2006 build is out.

<< < (2/2)

killerbot:
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 ....

Michael:
(Codeblocks crashes while dragging a docked window)
[/quote]

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

Michael

Szabadember:
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.

Michael:

--- Quote from: Szabadember on February 02, 2006, 04:47:30 pm ---That docking problem was already fixed...

--- End quote ---

Ah ok, I have misunderstood.


--- Quote from: Szabadember on February 02, 2006, 04:47:30 pm ---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 {/}.

--- End quote ---

Could you may be post the bug at SF?


--- Quote from: Szabadember on February 02, 2006, 04:47:30 pm ---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...

--- End quote ---

You can post a feature request at SF :).


--- Quote from: Szabadember on February 02, 2006, 04:47:30 pm ---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.

--- End quote ---

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

Ceniza:
Since the source formatter plugin relies on AStyle, the AStyle specific bugs should be posted in AStyle's project site @ SourceForge.

Navigation

[0] Message Index

[*] Previous page