Change Details

1) does exactly what I hoped for tested while running configure on a bigger in-tree build project like CodeBlocks with KDevelop configured to monitor directories for and reload them in case of changes. Not profiled formally, the effect is clear from following CPU usage in top, from fan noise, and from the runController buttons not turning on in the toolbar. 2) tested on Mac and Linux. Works as expected except for the fact that the initial project load puts TWO entries in the "stop individual job" dropdown menu. There are no duplicate proxies as far as can tell so this escapes me still.

1) does exactly what I hoped for tested while running configure on a bigger in-tree build project like CodeBlocks with KDevelop configured to monitor directories for and reload them in case of changes. Not profiled formally, the effect is clear from following CPU usage in top, from fan noise, and from the runController buttons not turning on in the toolbar. 2) tested on Mac and Linux. Works as expected except for the fact that the initial project load puts TWO entries in the "stop individual job" dropdown menu. There are no duplicate proxies as far as can tell so this escapes me still.

1) does exactly what I hoped for tested while running configure on a bigger in-tree build project like CodeBlocks with KDevelop configured to monitor directories for and reload them in case of changes. Not profiled formally, the effect is clear from following CPU usage in top, from fan noise, and from the runController buttons not turning on in the toolbar. 2) tested on Mac and Linux. Works as expected except for the fact that the initial project load puts TWO entries in the "stop individual job" dropdown menu. There are no duplicate proxies as far as can tell so this escapes me still.