Wireshark-bugs: [Wireshark-bugs] [Bug 553] Menu and Title bars inaccessible using GTK2 (non-lega

Date: Mon, 8 Oct 2012 06:41:59 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553

--- Comment #55 from kproth@xxxxxxxxxxxxxxxxxxxxx 2012-10-08 06:41:57 PDT ---
Chris - I just tried a test w/ 1.9.0-SVN-45380, attempting to reproduce the
issue as originally reported on a multi-monitor system.  I confirmed that it
seems to have been fixed, though as already noted, it has probably been fixed
for a while.

I also tried to validate the new logic for re-positioning to keep the
upper-left corner visible.  And I noticed that it's not taking the taskbar into
account.  If I place my taskbar at the top of the screen, wireshark's window
(including the entire title bar) can end up hidden by the M$ Windows taskbar.  

To reproduce on an XP SP3 system (probably doesn't have to be multi-monitor):

  1 - edit the recent_common file in the user's wireshark folder, and set
gui.geometry_main_y to a value larger than the bottom edge of the desktop (i.e.
set it to 1100 if your screen is 1280x1024).

  2 - move the M$ windows taskbar to the top edge of the screen

  3 - launch wireshark

  4 - observe that the resulting wireshark window's title bar is now hiding
behind the taskbar.

Does it make sense to ask you to look into this while you're fresh into this
part of the code?  Or should I file a new bug?  I'd attempt to fix it myself,
but I don't have a development environment setup, and I have no experience
developing Gtk-based UI code...  I did find a post from Gnome, that appears to
have dealt with a similar issue in their Gtk-based code: 
https://mail.gnome.org/archives/commits-list/2011-November/msg00521.html.  You
might also look at this post:
http://ntcoder.com/bab/2007/06/15/get-work-area-rectangle-along-with-main-rectangle-of-desktop/.
 The basic change is that you'd need to find a way to access the monitor
geometry that uses the "rcWork" structure from the underlying GetMonitorInfo
call, rather than the "rcMonitor" structure.  I don't know, however, if there's
a good way to do that while still following the normal coding constructs used
in the wireshark code-base.

~ Kevin

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.