For example, how about enabling pattern "trigger" for the Search function? That would enable us to capture and decode a long data sequence from a parallel bus including its handhake signals, then look for particular situations (patterns) on those lines and highlight them via search markers.
Well you would learn much more by not having this feature I think ![Smiley :)](https://www.eevblog.com/forum/Smileys/default/xsmiley.gif.pagespeed.ic.R8GFI-pF6f.png)
I was serious about this proposal. How would you currently deal with a data bus which addresses various devices, where you want to review all (!) write accesses to one particular device? You can
trigger on the desired combination of R/W and CS states, but then you will miss a lot of accesses during trigger re-arming gaps. But you cannot
search for this combination of states in a longer capture.
Not sure how serious
you are about the pain level caused by the lack of ASCII decoding.
![Roll Eyes ::)](https://www.eevblog.com/forum/Smileys/default/rolleyes.gif.pagespeed.ce.XcUK202Yqt.gif)
I never talked about "learning ability", by the way; not sure where you got that itch from.