Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Doxygen plugin
Cryogen:
Hi Guys,
I have been tinkering with some of the other plug-ins in my travels around C::B, as well. Of note is that I have added a new comment type to the ToDo plug-in to allow it to insert "\todo" lines directly into C-style doxygen blocks. The existing C++-type doxygen-style comment already does this well for C++-styled comments but none worked for C-styled blocks. The details are here:
http://forums.codeblocks.org/index.php/topic,12130.0.html
Cheers.
Cryogen:
Hey Joker,
Thanks for taking the time to report your findings, I really appreciate it.
--- Quote from: private_joker on March 06, 2010, 02:56:43 am ---Bug: if tabs w. sourcecode isn't open and you trying push "Extract documentation..." button, CB will crash.
--- End quote ---
Whoa doctor! That's not good. I've looked into this. In fact, the only button that does not crash C::B when there are no tabs open is the config. dialogue button. My code is never executed i.e. C::B crashes before it gets to my code. I can't trap it. I think that the config button may work because it uses a default plug-in function. Execution doesn't reach the first line of the function called by connect() to respond to the event. Morten, can you shed any light on this?
In the meantime the workaround is to ensure that you have at least one editor window open when running DoxyBlocks functions.
--- Quote from: private_joker on March 06, 2010, 02:56:43 am ---Bug: ExtractDocs.cpp:551
--- Code: ---ret = wxExecute (cmd + wxT(" ") + fnDoxyfile.GetFullPath(), sOutput, sErrors);
if(ret == 0)
{}
--- End code ---
--- Quote ---Execution of 'C:\Program Files\doxygen\bin\doxygen.exe' failed.
--- End quote ---
It seems like "if(ret == 0)" isn't fully correct. Maybe better use "if(ret != -1)"
--- End quote ---
From the docs: "In the case of synchronous execution, the return value is the exit code of the process (which terminates by the moment the function returns) and will be -1 if the process couldn't be started and typically 0 if the process terminated successfully."
I take your point. != -1 does seem to be more correct. I've changed it, thanks. Are you seeing a problem? You don't say.
--- Quote from: private_joker on March 06, 2010, 02:56:43 am ---Probably Bug: doxywizard isn't run.
--- Quote ---Running doxywizard...
Process 3308 (C:\Program Files\doxygen\bin\doxywizard.exe C:\Program Files\CodeBlocks\workspace\Codeblocks-Nightly\src\plugins\contrib\doxyblocks\doxygen\doxyfile) launched.
--- End quote ---
--- End quote ---
So you're seeing this message and then doxywizard doesn't appear? I'd say if a process number is returned then it ran. What happens after the process is spawned is not C::B's doing. I see, however, that you are using the notorious "Program Files" directory and I would guess that the space in the path is choking doxywizard. I would recommend never using Program Files for anything of your own and leaving it for Windows' use. Since doxygen is originally a Unix application I would think that it doesn't like spaces.
[Update:] I ran a check and, sure enough, doxywizard fails if I use a path to a doxyfile that contains spaces. DoxyBlocks should quote the path to avoid the problem. I'll fix that and upload it to SVN later today. Thanks.
I'd appreciate an update once you've tried it to let me know whether that fixes it for you.
--- Quote from: private_joker on March 06, 2010, 02:56:43 am ---I'm using self builded CB and self builded Doxyblocks. Both from SVN trunk.
Thank you & keep working on it.
--- End quote ---
Thanks. You can count on it. :P
Cryogen:
Uploaded 0.7.670. SVN revision 12.
Change log:
-Added: The block comment sample now updates to reflect the selection when "Use @ In Tags" selection is changed.
-Cleaned: Improved some text generation to simplify localisation strings.
-Added: Some missing documentation.
-Updated: Improved return value checking when running doxygen. Thanks to private_joker.
-Updated: Quoted the doxyfile path when running doxywizard to avoid doxywizard crash if the path contain spaces. Thanks to private_joker.
Cheers.
private_joker:
--- Quote from: Cryogen on March 06, 2010, 10:32:00 pm ---
Hey Joker,
Thanks for taking the time to report your findings, I really appreciate it.
--- End quote ---
No problem, I'd want too to comment my code, normally is look like:
// don't know how, but it works, thank you God. Amen.
:P
--- Quote from: Cryogen on March 06, 2010, 10:32:00 pm ---From the docs: "In the case of synchronous execution, the return value is the exit code of the process (which terminates by the moment the function returns) and will be -1 if the process couldn't be started and typically 0 if the process terminated successfully."
I take your point. != -1 does seem to be more correct. I've changed it, thanks. Are you seeing a problem? You don't say.
--- End quote ---
Now is working.
--- Quote from: Cryogen on March 06, 2010, 10:32:00 pm ---So you're seeing this message and then doxywizard doesn't appear? I'd say if a process number is returned then it ran. What happens after the process is spawned is not C::B's doing. I see, however, that you are using the notorious "Program Files" directory and I would guess that the space in the path is choking doxywizard. I would recommend never using Program Files for anything of your own and leaving it for Windows' use. Since doxygen is originally a Unix application I would think that it doesn't like spaces.
[Update:] I ran a check and, sure enough, doxywizard fails if I use a path to a doxyfile that contains spaces. DoxyBlocks should quote the path to avoid the problem. I'll fix that and upload it to SVN later today. Thanks.
--- End quote ---
Yep. Now is working too.
I know it sounds a bit pedantic but:
ExtractDocs.cpp:565
--- Code: ---if(sText.Length() > 0)
--- End code ---
I think
--- Code: ---if(!sText.IsEmpty())
--- End code ---
is better :)
PizzaNapoli:
Hi, everybody
I have the same problem as "codeur" in "Reply #12".
Unfortunately I can't install that plugin.
I use this CB version: Release 8.02 (2008-02-27 19:55:16) gcc 4.2.1 Windows/unicode on a Windows XP SP2
Now I'm not sure if this problem was solved, and if yes how ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version