It would be helpful when analyzing a trace if the start/duration times of the function block under the cursor were listed in the cursor line (currently you have to zoom in far on each endpoint and record the numbers yourself). These times should use an appropriate unit (eg. 100ms not 0.1s), falling back to hh:mm:ss.sss for very large values. The precision should (probably) be configurable (unless 9 digits past the decimal is still small enough to fit in the line).
IMHO this should only consider the function block as rendered, so if there's a 1-sample break it will still consider it one block. If this is considered two blocks instead, the "real" block under the cursor should be highlighted.
It would be helpful when analyzing a trace if the start/duration times of the function block under the cursor were listed in the cursor line (currently you have to zoom in far on each endpoint and record the numbers yourself). These times should use an appropriate unit (eg.
100ms
not0.1s
), falling back tohh:mm:ss.sss
for very large values. The precision should (probably) be configurable (unless 9 digits past the decimal is still small enough to fit in the line).IMHO this should only consider the function block as rendered, so if there's a 1-sample break it will still consider it one block. If this is considered two blocks instead, the "real" block under the cursor should be highlighted.
Motivating example:
Here I would like the cursor line to read: