User forums > Nightly builds

The 16 January 2010 build (6088) is out.

<< < (27/28) > >>

critic:
I want to requiest a new feature - adding files right to the virtual folders in the project's tree. Is it possible?

I use my libraries at sources level (without precompiled binaries .so or .dll, or .a) and that's why I need to add sources directly to project. When I add files to project from outside of project's directory all project's files names became large that is not friendly. But when I split these files in virtual folders - all OK - one virtual folder for each library.
Now, to add files to virtual folder I need to add them to project's root, then move them one by one to virtual folder created before. It will be better to allow multiple selection of files in project's tree for such operations and allow addition of files to concrete virtual folder as to the project's root node

loopcoder:
As many "cross-platform-coders" I work on Linux and Windows at the same time.
The class browser (symbol pane) and the code completion do not work for me at all - and luckily I found the reason (just minutes before wiping C::B off my hard drive... ;) )

The parser cannot handle stream comments ("//"), if the EOL mode does not match the current OS (e.g. just CR in Windows). That is quite often the case, if you do the main development under a pleasant OS and want to make it work in a Windows environment...

Small sample: (save it to a unix file (just CR) )

class Foo {
public:
   int this_is_parsed;  // knock-out comment
   int oh_thats_bad;
}


That bug may also apply for other EOL modes (Mac..)


regards


 

critic:
I use UTF-8 charset and LF end of line - it works fine. Earlier I used cp1251 with CRLF - it worked fine too. CF is MAC end of line. If you work under windows and linux (not MAC), why do you choose CF?

EDIT:
May be it's charset and `end of line` incompatibility? Which charset do you use?

loopcoder:
Yes, sorry, I have mixed up CR (\r)  and LF (\n).

The point is: the syntax parser does not work, if you have single line comments ("//...") in a mac file (CR) using C::B in Windows (maybe as well in other non-Mac systems).

If you share your files, such situations may occure.
I consider this as a bug, since you expect the parser / the class browser / the code completion to work in any environment and setting -- you will always blame the software, not your settings ;)
The syntax parser should accept both '\n' and '\r' as EOL. No big deal.    

critic:
@loopcoder
+  :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page