In case of MessageViewer instances, CommandInvocation attributes exitCode, stdout and stderr are ignored and the matching UI elements are hidden in the editor dialog. However, these could be used in cases where no sensible filter could be defined or the filter is not enough in itself.
In such cases these filters would be evaluated just like as if they're part of a MessageMatch filter, but if there's a match, the output is reused to fill the contents of the message viewer UI. This would make sense for Protocol Buffers for example, for which there's no easy-to-define filter, as the only certain way to determine validity is to do the actual parsing.
In case of
MessageViewerinstances,CommandInvocationattributesexitCode,stdoutandstderrare ignored and the matching UI elements are hidden in the editor dialog. However, these could be used in cases where no sensible filter could be defined or the filter is not enough in itself.In such cases these filters would be evaluated just like as if they're part of a
MessageMatchfilter, but if there's a match, the output is reused to fill the contents of the message viewer UI. This would make sense for Protocol Buffers for example, for which there's no easy-to-define filter, as the only certain way to determine validity is to do the actual parsing.