-
-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show date of Zniffer captures #4115
Comments
@AlCalzone I would be for the date in details, WDYT? |
We had that at the start and it would take up too much space for short captures. Maybe have Z-Wave JS UI check if the first and last capture frame are on different dates and then show the date? |
What about a tooltip when I hover over the time? Not exactly discoverable, but maybe good enough. What kind of device are you trying to optimize for where it would take up too much space in the details pane? Here's the same trace opened in the SiLabs Zniffer in Windows: Even with date as column, there's no problem showing all the information on a laptop with 1980x1080 resolution scaled to 125% (I realize the browser does take up a bit more UI space though). Related to the date and time, any idea what's going on in the SiLabs Zniffer? Is it expected that loading a ZLF generated from Z-Wave JS is compatible? The timestamp shown in ZUI is the correct one, while SiLabs is shifted, and obviously the date is wrong no matter which way it's read. |
The Z-UI Zniffer has quite a bit more padding around the data. We might need to reduce that even further, because right now it doesn't come close to the information density of the offical application. As for the timestamps, this is one of the known open issues: |
Could this be a valid solution? |
Is your feature request related to a problem? Please describe.
The zniffer captures show a timestamp but no date. If I have a multi-day capture I might not remember which timestamp goes with which date.
Describe the solution you'd like
Describe alternatives you've considered
None
Additional context
The text was updated successfully, but these errors were encountered: