| Bug ID |
11855
|
| Summary |
IO graph scale in Y axis is labelled as packets/s but values are packets/interval; change of interval size throws the curve out of focus
|
| Product |
Wireshark
|
| Version |
2.0.0
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14120 [details]
usb isochronous transfer at 100 URBs/second
Build Information:
Version 2.0.0 (v2.0.0-0-g9a73b82 from master-2.0)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without
AirPcap.
Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (with SSE4.2), with 8141MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 31101
--
May depend on data type so I better add the particular capture file on which
I've observed it.
1. "Statistics -> I/O Graph" opens a window with the graph and sets scales so
that the actual graph is visible, good. The only issue here is that while the Y
axis values are shown in packets/interval, the label says "packets/s" rather
than (static) "packets/interval" or (variable and more informative)
"packets/[1|10|100][s|ms|μs]". The other way round, i.e. keeping the label
static as packets/s and really show values in packets/s regardless the interval
size is a bad idea because
- for intervals > 1 s, users could be confused by values of fractions of
packets per second,
- the horizontal resolution would be insufficient for short intervals.
There is a negative side to changing the scale, however, which consists in the
fact that any click to the graph itself, regardless whether it actually changes
anything or not, switches off the auto-rescale on change of interval size, so
when the user changes interval size, the curve may disappear from the graph
window completely, but the state of auto-scale is not indicated anywhere. So a
tickbox "reset Y-scale at interval size change", active by default, would be
nice. My personal opinion is that there are just a few cases where the user
would needs to keep the Y scale unchanged after change of the interval size. On
the other hand, reset of the whole graph is too big a hammer.
You are receiving this mail because:
- You are watching all bug changes.