User forums > Nightly builds
The 16 September 2014 build (9916) is out.
raynebc:
I'm seeing the same issue with the cursor, running Windows XP x64. The July 6, 2014 nightly does not exhibit this behavior on the same computer. If it helps track down the offending change, let me know and I'll test each of the nightly releases in between.
I'm finding that an old bug still occurs where CodeBlocks correctly reports the file size of a source file in my project, but reports the line count as 0 and when I double click on the file from the manager window, it opens the file as if it was empty:
http://forums.codeblocks.org/index.php/topic,18580.msg128907.html#msg128907
I copied the file to the root of my project and added that new copy to the project, but it also opens as if it was empty. I copied a file that opens properly in CodeBlocks to that path (\src\alogg\src\) and it opens and displays normally. It seems CodeBlocks has some kind of issue with this file in particular, which is available here:
https://editor-on-fire.googlecode.com/svn/trunk/src/alogg/src/alogg.c
White-Tiger:
raynebc, well if that file is a problem, the uploaded one seems fine to me... so because of line ending conversation done by SVN and FTP, etc., can you maybe ZIP it or something?
@CB:
I've got one question myself.. is it possible to add scopes / more scope to the codecompletion?
IIRC it can handle normal scopes {}, but what about "global" variables declared static in one file? Currently I see every static variable or function in every file... this doesn't only make it hard for me to find variables for the current file, it's also confusing functions... I've got multiple files with functions with the same name (one file per dialog subpage), and when I try to open the declaration/implementation I end up being thrown to a different file... sometimes it doesn't even detect all functions in the current file.. (not sure if it's related)
So please let the parser respect the "static" keyword.. Since it does know about scopes, it shouldn't be too hard to handle it as one.
scarphin:
I think the behavior of cursor blink is like it's scanning the whole blink period range with a certain increment, after that decrement the period range and then loop over again and again. At least on Windows.
raynebc:
--- Quote from: White-Tiger on September 18, 2014, 12:21:51 pm ---raynebc, well if that file is a problem, the uploaded one seems fine to me... so because of line ending conversation done by SVN and FTP, etc., can you maybe ZIP it or something?
--- End quote ---
Here's the zipped file:
http://www.mediafire.com/download/sdnbmgggd9m7duc/alogg.zip
Aleksandr:
Hi,
found a couple of things related to doxygen that I think are incorrect.
Looking ahead to say, the project directory tree looks like this:
--- Code: ---project/
bin/
debug/
release/
build/
doxygen/
doc/
--- End code ---
In the build/ directory is a project file project.cbp. In the doxygen/ directory is a file doxyfile. debug/ and release/ is the directory in which the executable files are placed. And directory doc/ where doxygen generates html.
Firstly, perform the menu item DoxyBlocks→Doxywizard...
When the project has just opened and when menu item performed in the tab DoxyBlocks displays the following output:
--- Code: ("DoxyBlocks tab output") ---Running doxywizard...
Process 16240 (C:\Program Files\doxygen\bin\doxywizard.exe C:\Users\Aleksandr\Code\C++\project\build\doxygen\doxyfile) launched.
--- End code ---
And in the opened dialog one can see that the file doxyfile was successfully readed.
But after has been run one of the targets (debug or release) the output changed to the following:
--- Code: ("DoxyBlocks tab output") ---Running doxywizard...
Process 22804 (C:\Program Files\doxygen\bin\doxywizard.exe C:\Users\Aleksandr\Code\C++\project\bin\debug\doxygen\doxyfile) launched.
--- End code ---
or
--- Code: ("DoxyBlocks tab output") ---Running doxywizard...
Process 17736 (C:\Program Files\doxygen\bin\doxywizard.exe C:\Users\Aleksandr\Code\C++\project\bin\release\doxygen\doxyfile) launched.
--- End code ---
respectively. It is obvious that the file is not readed. But, perform the menu item DoxyBlocks→Extract documentation is still correct.
Secondly... well, it probably does not apply to the C::B, but to the plugin DoxyBlocks. I don't know.
So, as you can see the directory tree before, doxygen is configured to put everything in the directory doc/. Nevertheless, after extracting documentation path in a message about the location of the generated document is invalid:
--- Code: ("DoxyBlocks tab output") -------------------------------------------------------------------------------------------------------
Extracting documentation for project.
DoxyBlocks is working, please wait a few moments...
Found existing doxyfile...
Success.
Your documents are in: C:\Users\Aleksandr\Code\C++\project\build\doxygen\
Done.
--- End code ---
And perform the menu item DoxyBlocks→Run HTML fails:
--- Code: ("DoxyBlocks tab output") ---Index.html not found at C:\Users\Aleksandr\Code\C++\project\build\doxygen\html/index.html.
--- End code ---
Thats it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version