Hey Joker,
Thanks for taking the time to report your findings, I really appreciate it.
Bug: if tabs w. sourcecode isn't open and you trying push "Extract documentation..." button, CB will crash.
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.
Bug: ExtractDocs.cpp:551
ret = wxExecute (cmd + wxT(" ") + fnDoxyfile.GetFullPath(), sOutput, sErrors);
if(ret == 0)
{}
Execution of 'C:\Program Files\doxygen\bin\doxygen.exe' failed.
It seems like "if(ret == 0)" isn't fully correct. Maybe better use "if(ret != -1)"
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.
Probably Bug: doxywizard isn't run.
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.
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.
I'm using self builded CB and self builded Doxyblocks. Both from SVN trunk.
Thank you & keep working on it.
Thanks. You can count on it.