Probe Watch Window - Last Update - Show milliseconds instead of date

[bbean]

This may have been proposed before but here goes anyway.  I don't usually watch the probe window over periods of a day or more.  I know that there may be some rare occasions that this might be beneficial, but it would be much more useful to see milliseconds in the Last Update column.  This would allow for quick but rough performance testing by placing a bunch of probes inline on an error string for instance.

[dthor]

I'm not fond of the "Insead of" part, but I think that the core of the idea is good: some things happen so fast that you need to be able to see time in ms.

[SteenSchmidt]

I think the timestamp should remain. A simple fix would be to just expand the existing probe timestamp to include ms. Often this isn't enough to determine the sequence of value updates though, as many updates can happen in the same ms.

/Steen

[ThiCop]

Maybe it could be useful to have an option to switch between ms and date/time stamp view.
In the ms view it could also be useful to only see ms and be able to specify a zero reference point.

[SteenSchmidt]

Yes, because there is no natural zero reference point for the probe view, a the probe view knows nothing about when execution started for the context you're viewing. The zero reference point can't be the first probe value as that would erroneously make it look like your app may have started execution at that point in time (which it probably didn't). Cheers, Steen

[bbean]

agree with steen, just show me the milliseconds. Or give me the ability to right click on the column and update the format of the date.

[Mike_Le]

An additional fix for this would be the option to sort probes by Last Updated.

It would be nice if you could sort based on the Headers of probes in general.

[David_Staab]

I would only support this change if it were implemented as a toggle between the two views. I often use the timestemp to determine whether a probe was updated on my most recent execution of the program.