https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2724
Summary: bad window position on startup (partly offscreen) and
not saving window position either
Product: Wireshark
Version: 1.0.2
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: quartz12h@xxxxxxxxx
Build Information:
wireshark 1.0.2 (SVN Rev 25698)
Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
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 with GTK+ 2.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt 1.4.1, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.
Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
--
The wireshark application starts at a bad window position, and the window
position I chose to correct is not restored on the next start.
My desktop is made of 2 monitor, a primary on the right and a secondary on the
left, about 400 pixels lower than the primary. Both are 1280x1024.
The wireshark window is not showing on the primary display but on the secondary
display (on the left) yet the top the frame is aligned with the top of the
primary on the right.
As a result, there is not access to the menu bar at all; it is completely off
screen.
The only workaround is to used the windows "move" (alt-space, M, hit an arrow
key and then move the mouse to reposition).
A simple fix would be to save the window position on exit, and restore on
startup.
A better fix includes the previous one, but in abscence of saved positions, the
program should not attempt to position the window, only give it a dimension and
let the Windows position the frame X-Y location.
The saved positions MUST be challenged by the actual current screen dimension
(in case it changed), but the preferred way is to not assume the x=0 and y=0
are a viewable position. There should be an API in win32 to describe the
monitors, including the primary monitor bounds; hat should be enough.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.