Wireshark-bugs: [Wireshark-bugs] [Bug 11919] New: IO Graph: Don't set default action to "Save As
Date: Tue, 22 Dec 2015 16:41:42 +0000
Bug ID 11919
Summary IO Graph: Don't set default action to "Save As" button
Product Wireshark
Version Git
Hardware x86
OS Windows Server 2008 R2
Status UNCONFIRMED
Severity Minor
Priority Low
Component Qt UI
Assignee bugzilla-admin@wireshark.org
Reporter carstengrohmann@gmx.de

Build Information:
Version 2.0.1rc0-215-g3a28602 (v2.0.0-215-g3a28602 from master-2.0)

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 (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 Server 2008R2 Service Pack 1, build 7601, with
locale
C, without WinPcap, with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Six-Core AMD Opteron(tm) Processor 2431, with 65533MB of physical memory.


Built using Microsoft Visual C++ 12.0 build 31101

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Dear Wireshark Developer,

please rework the handing of the event triggered by pressing the return key.

Currently it's very uncomfortable if you inadvertently press return to finish
the definition of a new added graph and the "Save Graph As" pops up.

Thereby I suggest you to change the reaction of pressing return, depending if
the user is editing a graph definition or not.

Inside the edit mode, return should should finish the edit mode.

Outside the edit mode, return should trigger "Save As" like now.

Regards,
Carsten


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