Yay for the H/L markers! They seem trivial, but when it comes to figuring out if the interrupt line is stuck high or low (that can be important to know) the markers make it instantly unambiguous.
One thing I’ve been wishing for is the ability to shrink the left hand channel name column down to just wide enough to see all of the labels I’ve given. Like you can do in Excel basically.
I’m really liking the improvements to the data table. I’m using it for I2C and it is really getting there. A couple of suggestions to improve usability.
The “READ” column reads “true” and “false” It looks like a “false” read is a write. Couldn’t the column be named “Operation” and the entry “Read” or “Write”? That seems much clearer.
It would also be nice if the table address decoding tracked what I have setup in the Analyzer. In the case below, I have the Analyzer setup for 8 bits, ignore the R/W LSB. The trace label correctly displays 0x0A. The table shows Address 50. I should have to do left shifts in my head. The table should also show 0x0A.
I’m really liking the improvements to the data table.
Thanks
The “READ” column reads “true” and “false” It looks like a “false” read is a write. Couldn’t the column be named “Operation” and the entry “Read” or “Write”? That seems much clearer.
You’re right, it is clearer. The downside is that we’ll break the API for HLAs that use I2C. We’ll have to think about it a bit more…
It would also be nice if the table address decoding tracked what I have setup in the Analyzer
I agree! This feature is on our roadmap, though we don’t have a timeline yet.
There is a whole bunch of details I’ve reported earlier that haven’t been addressed yet in release 2.3.2. I’ve numbered the questions for easier management.