| Bug ID |
12827
|
| Summary |
I/O graph missing human readable Y Scale like it was in 1.x version
|
| Product |
Wireshark
|
| Version |
2.0.5
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14883 [details]
Example image bits/s
Build Information:
Wireshark 2.0.5 (v2.0.5-0-ga3be9c6 from master-2.0)
Copyright 1998-2016 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.11.0, 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 10, build 14393, with locale German_Germany.1252,
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) i7-3840QM CPU @ 2.80GHz (with SSE4.2), with 16322MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 40629
--
The actual version of QT I/O Graphs interface shows a bad human readable Y
scale unit.
If the Unit is Pakets/s or Bits/s we have in QT interface values like 2.8*10^7
This is something most pople have to think about which value it is. The old
version have shown the total number of zeros, even if there where some more.
See example image. This was much better readable than the new format, but it
could be better.
Example image shows Bits/s as max value in Y Scale
QT Interfaces: 2.8*10^7
old Interface: 50000000
In both pictures, the highest value is about 28Mbit/s
I would suggest a human readable Y scale with a unit of "Mbit/s". In my
example, a unit of 28Mbit/s would be perfect.
Suggestion: If a values is reaching 1*10^3 or a multiple of it, the unit should
scale automatically with the correct naming of the unit, like Kbit/s, Mbit/s or
Gbit/s. This makes it very easy to read the scale!
You are receiving this mail because:
- You are watching all bug changes.