Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Doxygen plugin
Jenna:
--- Quote from: Cryogen on March 18, 2010, 03:46:30 am ---I think Jens is the Linux man so we'll just have to wait for him to have the time, I guess. :evil:
--- End quote ---
--- Quote from: codeur on March 18, 2010, 07:30:59 am ---My advice: take the rest of the week and the week-end off. Spring is coming (if you are in the Northern hemisphere), take your girl out for a great bushwalk and come back refreshed. The blasted code can wait.
--- End quote ---
I'm at work until friday (most likely late) evening, until 9 or 10 pm each day (I have internet just since half an hour here after fighting the whole week with german telecom and some ignorant builder who cut our phone cable multiple times).
I hope I will find the time to look into it at the weekend.
But it worked for me without problems (automake and build by C::B).
If you build with automake-system, devel directory is not used.
Cryogen:
Hi Guys,
Released version 1.2.138 of DoxyBlocks
-Fixed: The menu activation code was still not right. I think I now have the right combination of events to make things happen correctly.
Hurrah! :o
Cryogen:
Hey Codeur,
Firstly, thanks for making the effort to test it. We need more users/developers like you! :P
--- Quote from: codeur on March 18, 2010, 07:30:59 am ---
--- Quote from: oBFusCATed on March 17, 2010, 10:47:43 pm ---codeur: start C::B with "codeblocks.exe --debug-log" this option adds another log pane
--- End quote ---
Thanks for the tip oBFusCATed. The message I get in the debug log when DoxyBlocks fails loading is... failed :shock: :? :lol:
I am confident this info will solve all of Gary's issues.
--- End quote ---
Awesoooooooooooome. :wink:
--- Quote from: codeur on March 18, 2010, 07:30:59 am ---Another one for you Gary. I built 1.1.123, removed the old plugin, installed the new one. No luck.
Steps to see the issue:
1- Install doxyblocks from .cbplugin (with an open project). DoxyBlocks menu and toolbar come up enabled.
2- Close all projects. DoxyBlocks menu and toolbar are disabled (greyed out).
3- Close CB, Open CB. The toolbar is disabled, the menu is enabled.
--- End quote ---
:cry:
The problem here is that the MENUBAR_CREATE_END event appears to be raised before the plug-in menus are processed. I'm not sure that that's right i.e. as it should be. PLUGIN_ATTACHED occurs far too early, before the menu is even drawn. I have therefore resorted to UPDATE_UI, which seems to be doing the job. I see that many of the other plug-ins use it, so maybe it's a common necessity. This time, I've tested it much more thoroughly and run it through all of the combinations of opening and closing projects, editors and the IDE that I can come up with and it is behaving correctly so far, including independently enabling and disabling the comment functions.
--- Quote from: codeur on March 18, 2010, 07:30:59 am ---My advice: take the rest of the week and the week-end off. Spring is coming (if you are in the Northern hemisphere), take your girl out for a great bushwalk and come back refreshed. The blasted code can wait.
--- End quote ---
Haha, good advice but it seems that I didn't listen. Perhaps on the weekend. :)
Fingers crossed.
codeur:
--- Quote from: Cryogen on March 18, 2010, 08:58:54 pm ---Hurrah! :o
--- End quote ---
Menu activation is working now (including the internal activation/deactivation of the comment functions), thanks.
Cryogen:
Hi Jens,
--- Quote from: jens on March 18, 2010, 06:19:02 pm ---I'm at work until friday (most likely late) evening, until 9 or 10 pm each day (I have internet just since half an hour here after fighting the whole week with german telecom and some ignorant builder who cut our phone cable multiple times).
--- End quote ---
Haha, everyone has their own struggle. :?
--- Quote from: jens on March 18, 2010, 06:19:02 pm ---I hope I will find the time to look into it at the weekend.
But it worked for me without problems (automake and build by C::B).
--- End quote ---
That would be great. Thanks. I have recovered C::B on Ubuntu so I now have the latest SVN running. I can still build my plug-in but all attempts to install it have failed. I also tried to integrate it into the automake build stream but that didn't work either. I don't know enough about it to see how it's done in C::B, generally.
The first thing I need to understand is why the the .cbplugin doesn't work, even in Windows where it works for me. The second is how to integrate it into the automake process. If I can build it along with the other contrib plugins it may work then. I guess the best thing would be to know what steps you take to get it working and just follow them.
--- Quote from: jens on March 18, 2010, 06:19:02 pm ---If you build with automake-system, devel directory is not used.
--- End quote ---
Ahah. That would explain a few things.
Cheers.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version