> See where this is going? I don't like it, and I bet users won't like it either. What am I missing? How should I go about sharing parse results between features, but still leave the user in control of when the feature should do its work?
The reason I'm asking, is because I figured that if I postponed the actual work until the user actively decides to refresh, and "cached" the parse results as they come in... well then I'd be refreshing a treeview and locating code issues in a possibly stale parse result... which literally brings me back to square one, where each feature works with its own…