Lee Thalblum

Working witgh 3.0.1.44 I found that in monitor mode the Freeze button doesn't seem to work any more. The screen kept scrolling even after I clicked the freeze button.

I tested 3.0.1.44 for a couple of days of reasonably heavy use. Works as expected, I didn't find any problems.

I'd go for the newline on direction change. As I originally mentioned, my problem, at least, was reading the data in larger binary data packets. Having each packet on a separate line would make things a lot easier. Thanks again forf looking into this. At 06:26 PM 10/22/2017, you wrote: I should point out that whereas it is probably a lot of work* to change the terminal component to have an interleaved two line mode, on the other hand, making monitor mode change to a newline at any direction change...

I'm working with binary data. And I've worked with several data scopes in the past (I remember several HP datascopes) that did what you're describing. At the end of the screen both lines wrapped around to the next line (or with a separating blank line). At 06:20 PM 10/22/2017, you wrote: What I was meaning is: in the case that RX and TX are on spearate lines, then pad them with spaces so that the interleaving is still apparent. This then begs the question about what the newline condition is? Is this...

I've used data monitors (both separate units and PC based) for quite a while (several decades, in fact). I've seen displays like you suggested, and also like: TX Data Rx Data Tx Data etc. i.e. on separate lines. I've found for short data packets interleaving as you suggested works fine. On longer data packets, it's easier to read when they're on separate lines. Just my opinion. At 07:27 PM 10/21/2017, you wrote: I am imagining that when either side gets a char, the other line has a space, so that...

Show data from each side on a separate line in monitor mode