Wireshark-bugs: [Wireshark-bugs] [Bug 11019] New: wireshark QT IO graph focuses "circle cursor"
Date: Sat, 28 Feb 2015 12:43:50 +0000
Bug ID 11019
Summary wireshark QT IO graph focuses "circle cursor" on old curve even the real-time curve has been unselected.
Product Wireshark
Version 1.99.x (Experimental)
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Qt UI
Assignee bugzilla-admin@wireshark.org
Reporter xiaochsu@foxmail.com

Created attachment 13480 [details]
second curve lest, first curve unselected

Build Information:
Version 1.99.3 (v1.99.3rc0-304-gefcd59e from unknown)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> 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 (32-bit) with Qt 5.4.0, with WinPcap (4_1_3), with libz 1.2.5, with
GLib 2.38.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, without PortAudio,
with AirPcap.

Running on 32-bit Windows 7 Service Pack 1, build 7601, with locale C, without
WinPcap, with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i3 CPU       M 350  @ 2.27GHz (with SSE4.2), with 2991MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 21005

--
wireshark QT IO graph focuses "circle cursor" on old curve even the real-time
curve has been unselected. Should IO graph switch the cursor focus on the
second real-time curve since first real-time curve has already been unselected
and curve disappeared on IO graph?

Issue reproduce step:
1) draw two real-time curves, "circle cursor" focused on first curve
2) unselect first curve, the "circle cursor" should switch to second curve, but
"circle cursor" still focused on the vanished first curve.

please refer attached two pictures for more clear view.


You are receiving this mail because:
  • You are watching all bug changes.