You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My team is using NSLogger also to display logs that were generated by field users. This means that the file might contain multiple days of logging. Thus, it would be really helpful to display also the day / month / year in the log message in UI.
I understand that this might take some width space from the actual message text. If that is a problem, we could have a button like "Show / hide function names" that toggles between a short date format and a long date format that also contains the day, month, year information.
If you think this change could be beneficial, I could make a PR with the change.
Thanks!
The text was updated successfully, but these errors were encountered:
Oops sorry, realizing I didn't answer this question.
I've had a discussion about this very feature with @stuffmc. I think the space problem can be solved by inserting markers every time the date changes. Optionally, we could make the marker stick at top while scrolling (or provide context any other way, i.e. in the bottom bar).
Yes, I think the marker + the marker stick at the top would work. Something similar to what Calendar application from mac OS is doing when Month view is selected. That would be awesome.
Hi,
My team is using NSLogger also to display logs that were generated by field users. This means that the file might contain multiple days of logging. Thus, it would be really helpful to display also the day / month / year in the log message in UI.
I understand that this might take some width space from the actual message text. If that is a problem, we could have a button like "Show / hide function names" that toggles between a short date format and a long date format that also contains the day, month, year information.
If you think this change could be beneficial, I could make a PR with the change.
Thanks!
The text was updated successfully, but these errors were encountered: