Hello Doug, At the moment there isn't, so that's what I'd do as well.Except maybe not across the entire sample range because you don't actually *know* what the entire sample range is in the PD. What's a suitable annotation length starting at sample #0? Yeah, I don't know either. :) -Soeren
On Tue, 2020-05-19 at 15:28 +0000, Doug Wegscheid wrote: > Is there a good way to tell the user that they have entered bad > options for a decoder in pulseview? > > I am looking at putting a stackable decoder that would filter based > on regexps on top of the UART decoder. The regexp option for the > uart_regexp decoder could be screwed up pretty easily. > > The best way I can think of is to put a big old annotation for the > entire set of input samples that tells the user what to fix. Is there > a better way? > > _______________________________________________sigrok-devel mailing > listsigrok-de...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sigrok-devel
_______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
