Yes, it’s time for another external annotator question! With the aid of some wise and helpful folks here, I’ve managed to integrate the aforementioned CLI-based static code analyzer very nicely. One thing that’s driving me a bit crazy, though, is that because this specific CLI can take a few seconds to execute for even a single file, it’s difficult to know when the editor is showing all of the information that it’s going to show.
I’ve noticed that doAnnotate() is executed under a progress indicator – specifically a DaemonProgressIndicator – but progress isn’t actually displayed anywhere, at least that I can tell. I’ve tried calling setText() on the active progress indicator hoping that might cause it to be displayed, but no go.
I’ve protoyped starting another background progress indicator while the CLI is executing, and that does provide one way to let the end user know that static code analysis information is still being gathered for the editor, but before I commit to that workaround, I figured I’d ask if there’s just some feature of external annotators to show progress more visibly and I just haven’t found it.
Oh, and importantly, this particular external annotator does not run when an editor’s document is dirty, so such a progress indicator would only ever be shown when a file is first opened in an editor tab and after an editor’s contents are actually saved to disk and no further changes have been made.