Summary: | add "Build Project" to the build toolbar, it doesn't appear | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Jon Smirl <jonsmirl> |
Component: | Build tools: Custom Makefiles | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | git master | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jon Smirl
2004-01-11 06:30:12 UTC
Doesn't matter which toolbar, icon doesn't appear on any of them. Hi Jon, it should appear as soon as you open a "buildable" project ( which is of course a cpp project i.e. ). If you have a buildable project open, there will be automagically a build-project button in the build toolbar ( which does NOT show in the configure toolbar dialog ) Some additional remarks: - Problems of this kinds is all due to a mixed usage of XMLGUI driven UI parts and not-XMLGUI driven UI parts - There are several things that currently can not be assigned a shortcut or toolbar icon to ( vcs operations etc. ) - Contextmenu is a way better point to have a look at - we should at least add a lot of XMLGUI driven UI stuff to our plugins. However, we're in deep freeze now. I did some more experiments, this seems to be broken only for custom projects. Kdevelop generated ones work ok. It might be better to have this icon always displayed and enable/disable it instead of having it appear and disappear. I definitely have a buildable project (custom c++ project imported from KDevelop-2), "Build Project" works from menu but doesn't appear in build toolbar (even if I add it in "Configure Toolbars..." Seems to be some problem with the Build toolbar and I suspect some wrong usage of XMLGUI. With an autoproject everything works fine (at first sight), but as soon as you try to configure the build toolbar you will find that in the config. dialog only the Stop button appears... Dupe against bug #118722, as it has a better description of the problem. *** This bug has been marked as a duplicate of 118722 *** |