Hi Matthew,
Wow, I didn't know about the hover trick, cool :-)
The use case is primarily a QOL improvement for discussions. Using your screenshot above, if I wanted to tell someone to take a look at the line you have hovered (before it got hovered), I would have to say "look at point four four zero one seventy two, close to the bottom" or similar. Instead, I would rather say "look at line 8" and immediately everyone in the call would know what I'm talking about. Over lengthy discussions this is a QOL improvement we've identified.
This also relates to the Bookmark bug I posted. If a non-default description is used, the rank is the only aspect identifying where the bookmark is in the log. But the rank means little to me since I've never seen which timestamps correspond to which ranks. If there was a rank column always in sight, I would already have an idea where I am in the log at all times, so when "rank 230313" is in a bookmark I would have some idea where it is. Again, this is not a big problem, just a QOL improvement.
Additionally, if someone looked at the trace log previously and has an interesting event, instead of communicating and searching for the lengthy / specific timestamp, the "Rank" column would allow just searching for the rank the other dev found (basically a "go to line" function).
I can't say I fully understand what is happening in the offset screenshot, but when I get some time I'll take a look more at this feature.
Thanks,
Zach
