gw0kin / gnome2-globalmenu

Automatically exported from code.google.com/p/gnome2-globalmenu
GNU General Public License v2.0
0 stars 0 forks source link

Opening global menus in GNOME panel changes menu bar to desktop menu bar, when used with fluxbox or sawfish #648

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install GNOME and set up the global menu bar (gnome-panel-2.32.1, 
gnome-globalmenu-0.7.10).
2. End metacity and start Sawfish (1.7.0.1) or Fluxbox (1.0.0).
3. Open a GNOME application (gedit-2.30.4).
4. Click one of the application's menus (File).

What is the expected output?

gedit's File menu should open.

What do you see instead?

The menu bar changes to the desktop menu bar, and the desktop's File menu opens.

What version of the Global Menu are you using? On what operating system?

0.7.10, on Linux.

What version of Vala are you using? (if your Global Menu is built from git)

N/A

Please provide any additional information below.

When using the metacity or openbox, the menus behave correctly. Within both 
fluxbox and sawfish, clicking a menu changes the menu bar to the desktop's.

Using sawfish, opening a menu using the keyboard also leads to the desktop menu 
bar. This works with fluxbox.

Using fluxbox, opening the menu from the "Main menu" applet changes the global 
menu bar to display the desktop menu bar. This works with sawfish.

Original issue reported on code.google.com by true...@gmail.com on 9 Dec 2010 at 10:49

GoogleCodeExporter commented 9 years ago
Could you make the gnome-panel window unfocusable in fluxbox?
It appears to me that fluxbox focused the panel window, although it carries a 
unfocusable hint. 

Original comment by rainwood...@gmail.com on 10 Dec 2010 at 2:29

GoogleCodeExporter commented 9 years ago
I don't know how to do that in fluxbox, but I do in sawfish, and there it 
doesn't help: I'm still getting the desktop menu.

Original comment by true...@gmail.com on 10 Dec 2010 at 7:32

GoogleCodeExporter commented 9 years ago
However, you are correct that the panel is getting the focus. Making sawfish 
print the name of the currently focused window when one of the global menu bar 
menus is opened prints "Top Expanded Edge Panel". Making it do the same thing 
when the "Main Menu" applet's menu is opened prints the name of the window that 
should be active -- "Terminal" in this test.

Original comment by true...@gmail.com on 10 Dec 2010 at 5:05

GoogleCodeExporter commented 9 years ago
Having looked into things a bit further:

> It appears to me that fluxbox focused the panel window, although it carries a 
unfocusable hint.

The panel is registered as a dock window, and while metacity and openbox make 
dock windows unfocusable, fluxbox and sawfish don't. There is no separate 
"unfocusable" hint that I could find, and 
<http://standards.freedesktop.org/wm-spec/1.3/ar01s05.html> only says 
"_NET_WM_WINDOW_TYPE_DOCK indicates a dock or panel feature. Typically a Window 
Manager would keep such windows on top of all other windows." so this part does 
not look like a bug/misfeature in any of the WMs.

The reason that even after forcing "never focus" to "yes" from within sawfish's 
configuration, it still didn't work, is because while sawfish's focus_out 
function ignores NotifyGrab/NotifyUngrab events, its focus_in doesn't, so all 
the usual focus stuff gets called when the menu bar asks for the keyboard. This 
part does look questionable on sawfish's part, and I'll ask about that on the 
sawfish mailing list.

Original comment by true...@gmail.com on 11 Dec 2010 at 1:38