Community
Participate
Working Groups
The Tasks filter is very useful, however on occasion, I load code I know is going to have a lot of compiler errors. Generally, this is because I want to browse or copy code from somewhere, but don't want to spend the time or effort rounding up all the external dependencies. When I select that project, the tasks view goes into hyper-computation-mode. Currently, I just deal with it for a while, and then close the project (which is a nice feature) but: I would like to be able to turn off tasks for a project. Of course, the granularity is arbitrary, the feature could also be implemented at the folder or compilation unit level -- but project seems easiest. This would be a compromise between closing the project and just dealing with the task lists CPU hungry ways. see bug 2792 see bug 5867 -Andrew
I believe there are plans for allowing users to "turn off" builders for certain projects. Would that satisfy your use case?
Yes, that would do. Assuming that a side effect of that is that existing tasks are removed when the builder is turned off (and not just that new tasks are not created). Also, it would be nice if this option was available at project- creation time.
*** This bug has been marked as a duplicate of 14441 ***
