Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Doxygen plugin
Cryogen:
Hey Codeur,
--- Quote from: codeur on March 16, 2010, 11:10:21 pm ---
--- Quote from: Cryogen on March 16, 2010, 08:04:01 pm ---...
-Added: The toolbar and menu are now disabled when all projects are closed and re-enabled when a project is opened.
--- End quote ---
There is something wrong with this (in my own Windows built that completes with 0 error 0 warning, I have not tried your .cbplugin). The menu and toolbar are disabled (greyed) when I close projects, but they are enabled when CB starts next on the "start here" screen (and no project loaded). CB then dies some time afterwards. I have to uninstall doxyblocks to retrieve normal behaviour. The previous version was not doing this even though it would somehow kill CB if you tried to configure doxyblocks with no project open.
--- End quote ---
Hmmm, OK. Please try the latest version. There was a problem with saving prefs that I have just fixed. Failing that, I'll need some steps that I can replicate because I'm not seeing that in my latest builds. As you can see below I have added some additional behavior around enabling and disabling the toolbar.
Also, for reference, I use the .cbplugin. I will go and try building it into debug and using update and see what happens after that, just to see if that changes things.
Cheers.
UPDATE: 1.1.111 is behaving normally after a rebuild and update in Windows SVN 6182 and the toolbar appears to be enabled/disabled appropriately now.
Cryogen:
I'm over-achieving today. 8)
Released version 1.1.111 of DoxyBlocks
-Updated: Made a matching HTML Help icon.
-Added: Block comments can now handle more than one return value keyword.
-Added: The toolbar is now disabled if there are no projects open on startup.
-Updated: Changed the log output when doxygen is running slightly.
Cheers.
LordCB:
Ok, I use NB 6181 for error please look at attachment thanx in advance
[attachment deleted by admin]
codeur:
--- Quote from: LordCB on March 17, 2010, 11:43:02 am ---Ok, I use NB 6181 for error please look at attachment thanx in advance
--- End quote ---
Same here. I even built svn 6190 in order to see if it improved things. It does not.
However I have always had this very same error (same one as LordCB) with Gary's .cbplugins. I have to rebuild doxyblocks myself to get it to work.
The current svn update claims to be 1.1.79 (1.1.111 not committed?). It builds and loads OK when I build it myself with SVN 6190 (after some minor modifications to the project).
What I get though with version 1.1.79 still has the same problem that the menu and toolbar are active when CB is just started (and CB dies if you open the DoxyBlocks preferences without a project open and then click OK), so I'll wait until 1.1.111 or later is committed to svn to see if Gary's fix worked.
Cryogen:
Hi Guys,
--- Quote from: codeur on March 17, 2010, 12:58:35 pm ---
--- Quote from: LordCB on March 17, 2010, 11:43:02 am ---Ok, I use NB 6181 for error please look at attachment thanx in advance
--- End quote ---
Same here. I even built svn 6190 in order to see if it improved things. It does not.
However I have always had this very same error (same one as LordCB) with Gary's .cbplugins. I have to rebuild doxyblocks myself to get it to work.
The current svn update claims to be 1.1.79 (1.1.111 not committed?). It builds and loads OK when I build it myself with SVN 6190 (after some minor modifications to the project).
What I get though with version 1.1.79 still has the same problem that the menu and toolbar are active when CB is just started (and CB dies if you open the DoxyBlocks preferences without a project open and then click OK), so I'll wait until 1.1.111 or later is committed to svn to see if Gary's fix worked.
--- End quote ---
It looks like I neglected to commit 1.1.111. Sorry about that. :oops:
It's committed now. That should fix the toolbar issue.
The error is interesting as that's exactly what I get when I try to install the Linux .cbplugin. The only things I can think of are that there is still something about my setup that is not as C::B expects or there's something wrong with the plug-in system. Since no-one seems to want to tell me what to do about it I can't do much. No-one seems to be using them, either, so maybe there's a reason for that. Interestingly, my Linux installation is the one that should be absolutely standard. It's the Windows one I have to fiddle with. I'm installing the .cbplugin into the setup that built it so maybe that's why it works for me, although that's exactly what fails on Linux. I'm going to try building the latest on Linux today and see if it'll get through the update process, just for kicks. In the meantime, I guess you should stick with building it from source.
The other issue I have is that C::B fails when I run the plug-in in debug mode. No idea why and no information provided by the IDE. I might play around with that and see if I can trace what's failing on Linux. It might shed some light on the problem.
BTW, did you check the application log as mentioned in the error? Please post the contents.
Cheers.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version