[01:36] <funkyHat> I suppose I should ask at a more sensible time of day ⡈)
[14:16] <tgpraveen12> n
[15:14] <tedg> bratsche: Do you have any thoughts on bug 553918 ?  It seems like we're grabbing keyboard focus, but Esc isn't giving it up.
[15:14] <ubot4> Launchpad bug 553918 in indicator-session (Ubuntu) (and 1 other project) "Keyboard shortcut usage blocks keyboard and other menus (affects: 1)" [Low,Confirmed] https://launchpad.net/bugs/553918
[15:14]  * bratsche clicks
[15:16] <tedg> What's weird to me is that hitting escape is odd on my session, but it's really bad in the guest session.
[15:18] <bratsche> Weird.
[15:20] <tedg> bratsche: I wonder if it's something with the panel window not having focus.  Like the menu closing is trying to give it to the panel, but that's not really possible?
[15:21] <bratsche> tedg: The fact that he says you have to click twice to open the menu makes me think there is still a popup window somewhere on the screen, like an empty menu or something.
[15:22] <bratsche> Or maybe I'm misunderstanding what his comment says.
[15:22] <bratsche> (comment #1, that is)
[15:23] <tedg> bratsche: Hmm, yeah.  I got it in a state once where it would highlight the "Applications" menu when I moused over it.  That's why I was figuring it was something with teh panel window.
[15:23] <bratsche> tedg: That's also related to some fuckedupedness of compiz, because I've seen stuff like that happen as well.
[15:24] <tedg> bratsche: I thought that too, but my guest session defaults to metacity.
[15:24] <bratsche> For some reason compiz seems to occasionally go into focus-follows-mouse mode for me.
[15:24]  * tedg likes focus-follows-mouse :)
[15:25] <bratsche> I'd like it better if it only happened when I explicitly enabled it. :)
[15:25] <tedg> Hmm, the same thing doesn't happen with Alt+F1 for the applications menu.
[15:26] <bratsche> Oh wait.
[15:26] <bratsche> I'm reproducing this here without doing C-s
[15:27] <bratsche> Oh wait, nevermind.
[15:27] <bratsche> I think that was just update-manager slowing down my system.
[15:32] <tedg> bratsche: Okay, in the panel they subclass the menu bar.
[15:32] <tedg> Here's the code that I think might be interesting but I don't understand :)
[15:32] <tedg> 437     menu_shell = GTK_MENU_SHELL (menubar);
[15:32] <tedg> 438     if (!menu_shell->active) {
[15:32] <tedg> 439         gtk_grab_add (GTK_WIDGET (menu_shell));
[15:32] <tedg> 440         menu_shell->have_grab = TRUE;
[15:32] <tedg> 441         menu_shell->active = TRUE;
[15:32] <tedg> 442     }
[15:32] <tedg> 443     gtk_menu_shell_select_item (menu_shell,
[15:32] <tedg> 444                     gtk_menu_get_attach_widget (menu));
[15:33] <tedg> That's when popping up a menu.
[15:33] <bratsche> But we're using a menubar as well aren't we?  Inside indicator-applet
[15:33] <bratsche> Or is that code from the subclass of menubar?
[15:34] <tedg> bratsche: That code is from the subclass.
[15:42] <bratsche> ted: Okay, so that code is actually just copied from _gtk_menu_shell_activate().  I think we're already doing the same thing.
[15:49] <tedg> bratsche: Why did they copy it then?  Seems like they could have just called gtk_menu_shell_activate() ?
[15:50] <bratsche> It's _gtk_menu_shell_activate(), not gtk_menu_shell_activate().
[15:50] <bratsche> It's not exported from libgtk
[15:50] <tedg> Yeah, I'm just assuming (still downloading gtk) that gtk* calls _gtk*
[15:51] <tedg> So it seems that they're avoiding something.
[15:51] <bratsche> Does Tomboy do this as well?
[15:52] <tedg> And, I don't think we're calling _activate, we're just calling _select_item... could that be the issue?
[15:52] <tedg> Perhaps we need both?
[15:52] <bratsche> Yeah, we need to activate it I think.
[15:55] <tedg> Tomboy is a StatusItem so it's all that XEmbed love -- it's a bit different.
[15:56] <tedg> bratsche: So I should activate the item, and then select it?
[15:57] <tedg> bratsche: The docs don't seem really clear.
[15:57] <bratsche> Yeah
[15:57] <bratsche> Try doing the same thing..
[15:57] <bratsche> if (!shell->active) { gtk-grab_add (shell); shell->have_grab = TRUE; shell->active = TRUE; }
[15:58] <bratsche> Maybe I should try to find out why activate isn't public.
[16:04] <tedg> I tried just calling the activate function -- no luck.
[16:16] <tedg> bratsche: That totally fixes it...
[16:16] <bratsche> Nice!
[16:17] <bratsche> Let's get that merged in :)
[16:17] <tedg> bratsche: Do you want to look at why, or should I just use that?
[16:18] <bratsche> tedg: No, I think I kind of already get it.  But I should try to look into making this public API.
[16:44] <Nafai> Hi guys
[16:45] <bratsche> hey
[16:45] <Nafai> Is there anything I can do to help debug the keyboard issues?
[16:45] <bratsche> It's fixed.
[16:45] <bratsche> Well, it will be once it's merged and released.
[16:46] <Nafai> oh sweet :)
[16:46] <Nafai> I have never known how to use the keyboard with the indicators I admit :)
[16:47] <bratsche> Well, the hotkey support is very new so you couldn't have done it until like yesterday. :)
[16:48] <Nafai> :)
[16:49] <Nafai> hmm, looks like I need to reboot into a new kernel, brb
[16:55] <Nafai> So what are the hotkeys?
[18:02] <jcastro> bratsche: yeah what are the hotkeys!
[18:02] <Nafai> I figured out two of them
[18:03] <Nafai> Super-s for the session and me menus and Super-m for the messaging menu
[18:03] <jcastro> super-m does some negative compiz effect for me
[18:03]  * jcastro will need to update
[19:02] <vish> tedg: hi... you on lucid right? and have inkscape installed? 
[19:02] <vish> do you have scrollbars when you open a image?
[19:02] <vish> seems i lost them in the last couple of days :(
[19:02] <tedg> vish: Just like opening an SVG file?
[19:02] <vish> tedg: yeah
[19:04] <tedg> vish: Yeah, are you sure you just didn't turn them off?
[19:04] <tedg> vish: They're in View
[19:05] <vish> tedg: oh , sry , i seem to have turned it off :s  
[19:05] <vish> i was trying a lot of stuff with the super+s being locked
[19:05] <vish> tedg: thanks :)
[19:06] <tedg> vish: No problem.  I like easy bugs :)
[21:36] <magcius> anybody around? For some reason, notify-osd isn't allowing me to click under
[21:47] <tedg> magcius: Yeah, it's an annoying bug :)  It should be updated soon.
[21:47] <magcius> tedg: do you know what causes it?
[21:48] <tedg> magcius: Only high level.  It was with gtk 2.20 and notify-osd setting input masks differently or something like that.  If you downgrade your GTK it also goes away.
[21:48] <magcius> tedg: ah
[21:49] <magcius> tedg: also, when I'm running uncomposited, the window doesn't hide, just the space around it goes black