Skip to content
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

Log playback does not reflect Range scaling used during collection #1066

Open
vshie opened this issue Nov 7, 2023 · 1 comment
Open

Log playback does not reflect Range scaling used during collection #1066

vshie opened this issue Nov 7, 2023 · 1 comment
Labels

Comments

@vshie
Copy link

vshie commented Nov 7, 2023

To replicate - create log file with multiple Max Ranges selected (e.g. 5m, 10m, 30m)
Next, open log for playback. Range can be set to 50m, or any value, and log will play back in this scale, but not scaled. Thus, targets that are measured at 2.5/5m range look like 25m/50m range.

Expected behavior - user cannot select Range during log playback. Playback updates with changes to range at relevant points in log file, based on what was recorded.
Pingviewer 2.4.1

Screenshots are the same moment of time in same log file, but with range set to different values.
Operating System: Windows 11
image
image

@ES-Alexander
Copy link
Contributor

For some extra context, this is discussed somewhat in #1011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants