Log in
| 1 | ||
| 1 | ||
| 1 | ||
| 1 |
I don't know why that solution slipped my mind. One element of the delay in doing a solution was the UI aspect. Between not knowing exactly what I wanted and some of the other downsides I had worried about, as well as other things being more certain improvements I always put time into other things when I was setting aside time for dev.
But @JasonCarswell had mentioned hover over. I'm surprised it slipped my mind for as long as it did considering I love hover over. So yeah. It's there. It may not be super obvious that it's there but it also keeps the UI compact which is a plus.
The current date-string I'm using is pretty verbose. I'm happy enough with it unless someone has a good suggestion for a better date-string.
Win. Win! WIN!!!
I love it!
Recommend going metric, larger to smaller Y/M/D H:M:S resulting in 2025-04-09 4:40:08 am EST. With military time and 24 hour you won't need am/pm. If your local browser interpolates the time then the EST won't be necessary unless you're referencing and communicating to/with others, and then I'd recommend the universal time in Greenwich and we can calculate if necessary, +5 for EST.
I am noticing a small bug where comments made since a process restart don't have a time. Let me see if I can fix that really quick.
Edit: This bug has been fixed.
Edit 2: Also it looks like said achieves showing the time not by being significantly wider but by using a much smaller font. Personally I like the chat being legible, but I could reduce the font size to squeeze a time in there if people are for it.
Don't mind a smaller font.
I'm guessing a screenshot could be taken, if ever a need arose.
To reference back to a time in chat is now possible, though with a little more effort and diligence, an acceptable compromise for less clutter.