The 06 January 2009 build (5382) is out.

[Loaden]

Hi, jens! I think i found the question. the 'Compiler's installation directory' can't support '$(CODEBLOCKS)', when i set this value to 'D:\ycdeng\qpcb\codeblocks\src\devel\bin', it's OK!
I hope you can fix it: not support $(CODEBLOCKS).
thanks!!

[attachment deleted by admin]

[Jenna]

Hi, jens! I think i found the question. the 'Compiler's installation directory' can't support '$(CODEBLOCKS)', when i set this value to 'D:\ycdeng\qpcb\codeblocks\src\devel\bin', it's OK!
I hope you can fix it: not support $(CODEBLOCKS).
thanks!!

That's what I wanted to write just in the same moment.
Where and how do you set $(CODEBLOCKS) ?

[Loaden]

Hi, jens! I think i found the question. the 'Compiler's installation directory' can't support '$(CODEBLOCKS)', when i set this value to 'D:\ycdeng\qpcb\codeblocks\src\devel\bin', it's OK!
I hope you can fix it: not support $(CODEBLOCKS).
thanks!!

That's what I wanted to write just in the same moment.
Where and how do you set $(CODEBLOCKS) ?

because the mingw install path is CB install path.

[Jenna]

I saw the compiler path in toolchain executables, but I didn't know (until now) that the variable is set automatically to C::B's executable directory when it starts.
Shame on me. :oops:

But I think that can be fixed, too.

Later this afternoon, or in the evening.

[Loaden]

But I think that can be fixed, too.
Later this afternoon, or in the evening.

Thanks you very much!

[d0c]

It seems that you forgot to update the maximum lexer constant in editorcolourset.cpp, making it impossible to use the proper lexer for the D programming language.
Patch for this and lexer_d.xml attached.

EDIT: Sorry, I missed that smart indent depends on the selected lexer. Patch updated

[attachment deleted by admin]

[ollydbg]

Hi, someone finds a bug in the Toolbar position.
See this thread
http://forums.next.codeblocks.org/index.php/topic,9890.msg69000.html#msg69000
I have verified that this bug exists in SVN5382.
Thanks.

[JMP]

Hi,

I have found that when dragging selected text beyond the actual extent of the editor area, there is not any auto-scroll, so one must drop the dragged selected text only on the visible area of the editor.

I remember, in some previous version of C::B, that auto-scroll worked as expected. Maybe it is because of the new scintilla version?

Regards

[olelukoie]

Hi,

I've got a problem compiling C::B as an rpm-package for current development version of Mandriva Linux 2009.1 distribution. I guess the problem is that when building rpm packages this distribution forces the use of GCC option -Werror=format-security and it produces several error messages like this:

Code Select Expand

wiz.cpp: In member function 'void Wiz::CopyFiles(cbProject*, const wxString&, const wxString&)':
wiz.cpp:757: error: format not a string literal and no format arguments
make[4]: *** [wiz.lo] Error 1
make[4]: Leaving directory `/home/olelukoie/rpmbuild/BUILD/codeblocks/src/plugins/scriptedwizard'

Is it possible to fix and make C::B compilable with this option? (As I said there are several other messages of the same error type).

[ollydbg]

Hi,

I have found that when dragging selected text beyond the actual extent of the editor area, there is not any auto-scroll, so one must drop the dragged selected text only on the visible area of the editor.

I remember, in some previous version of C::B, that auto-scroll worked as expected. Maybe it is because of the new scintilla version?

Regards

Verified. I can only drag the text to anywhere in the current view. auto-scroll can't work when dragging. But I don't think it's due to the new scintilla version. I can reproduce the bug in SVN5322.

[JMP]

Hi,

I also found that code completion toolbar (function location section) does not recognise functions defined in stored opened files(tabs). Only files opened during the current sesion are properly parsed and their functions located.
To reproduce this error, open first a project with multiple files, then open some files in the editor. Check that the code completion toolbar is locating all the functions in the files properly. Then "save everything" and exit C::B. Reopen C::B and select the last project. All opened files of the previous sesion are in the editor, but the code completion toolbar does not show any function.
Open some file of the project that was not already open. Code completion toolbar can locate the functions of this file, but not of the others.

By closing all tabs and opening again the files, code completion toolbar shows the functions properly.

Best regards
JMP

[Jenna]

But I think that can be fixed, too.
Later this afternoon, or in the evening.

Thanks you very much!

Should now also work with environment and global (C::B) variables.

svn r5399

[shurecki]

if you use slashs in the project name, like 'my/project/name' code blocks will create the folder name/my/project/name and creates the project there

and if you project's name ends with a slash it is stranger, it creates a '.cbp' foder and a '.cbp' project file

is this a bug?

[dje]

Well,

project name is used for file names.
At least on windows, there is a list of forbidden chars in filenames such as:\/:*?"<>|
So if you think it is a bug, let's write to M$

Dje

[Grom]

What about new components in wxSmith? Would be grate to have all of then inside. With full paletter it might become a real development toolkit. Also would be grate to have a menue, status bar and toolbar on the devlopment window.