Summary: | Rewrite/Redesign Run settings to work across projects and allow for extension from plugins | ||
---|---|---|---|
Product: | [Developer tools] kdevplatform | Reporter: | Manuel Nickschas <sputnick> |
Component: | run support | Assignee: | Andreas Pakulat <apaku> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | amantia, kdevelop-bugs-null, mcguire |
Priority: | HI | ||
Version: | unspecified | ||
Target Milestone: | 1.0.0 | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Manuel Nickschas
2009-02-04 14:24:29 UTC
*** Bug 178452 has been marked as a duplicate of this bug. *** *** Bug 182771 has been marked as a duplicate of this bug. *** Had a quick look at the problem and I think the base problem is that the run settings as is simply are not meant to be written as kcm using kconfig_compiler. They try to provide their own kcfg-code, but somehow its not hooked up to the gui properly. As there's a complete redesign planned anyway, I'll leave this one open for that, but there's no good way to fix the current dialog to behave properly without introducing ton's of connect() calls for all the widgets (which I consider wasted time given that this will be redone anyway) changing the title to match the actual plan for run settings: - possibility to have global runs, per-project runs - ability to re-use runs for debugging - ability for plugins to provide new run types including custom config pages this has landed in trunk now. |