[Bug 78204] "Execute" shouldn't be available if there is no executable target.
apaku at gmx.de
Mon Jun 30 12:11:54 UTC 2008
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
------- Additional Comments From apaku gmx de 2008-06-30 14:11 -------
Hamish I think I don't quite understand. Its important that our run-support doesn't depend on a project being open. I don't think we need to disable the action when the config is wrong and with the above I don't see why "run" should be disabled when no project is open. Unless you're talking about a 'run the default target in current project' action, which is completely wrong in itself. There's no "current project" and there surely is no "default" target. Running a target of a project should be a context-menu entry in the project tree (or anywhere else a project context is created) and we should have a way of re-running the last "execution".
So actually I think we should close this as fixed or wontfix, as KDevelop4 will always allow to run something, no matter what projects are open.
More information about the KDevelop-devel