=== chaotic_ is now known as chaotic
=== chaotic_ is now known as chaotic
=== chaotic_ is now known as chaotic
=== chaotic_ is now known as chaotic
=== MacSlow is now known as MacSlow|lunch
[16:13] <qense> jcastro: bug #550140 (and others) are the result of the practise of using a regular MenuItem for showing an application in AppInd, not a checkbox. You can only make the application visible with those entries, but not hide them. However, I've always used checkboxes so people can hide the window as well and can see whether the window is being shown in case they've lost it. What should we do? If we keep following the first option we should mark the bug I
[16:13] <qense>  mentioned as Won't Fix. Personally I would go for checkboxes.
[16:13] <ubot4> Launchpad bug 550140 in nautilus (Ubuntu) (and 1 other project) "File Operations does not Hide when Clicked (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/550140
[17:03] <qense> tedg: What do you think of bug 552920? Do you agree with the proposed solution: a delay?
[17:03] <ubot4> Launchpad bug 552920 in indicator-application (Ubuntu) "Autoexpanding indicator menus hurt usability (affects: 1) (heat: 14)" [Undecided,New] https://launchpad.net/bugs/552920
[17:05] <tedg> qense: Could be interesting, but I think that's a GTK bug.  We don't want to special case that in the indicators.
[17:05] <tedg> bratsche: What do you think? ^^  I thought there was *some* delay already?
[17:12] <bratsche> I guess I'm confused by what you mean by auto-expanding.
[17:12] <bratsche> Does that just mean opening the menu?
[17:13] <tedg> bratsche: Yeah.  Basically too quickly.
[17:13] <tedg> bratsche: Did you see the image in the attachement?
[17:13] <tedg> (assume I spelled that correctly)
[17:13] <bratsche> Right
[17:15] <bratsche> Okay, so gtk+ has something internal called (I think) a stay-up triangle.. but as far as I know, it's only used when dealing with submenus from a menu.
[17:16] <bratsche> But try to envision a menu with several menuitems, and the first menuitem has a submenu with several menuitems.  Your mouse is currently over the top menuitem of the parent menu and the submenu from it is open to the right.
[17:17] <bratsche> Now when you move the mouse toward say the middle of that submenu, you'll probably mouse-over a menuitem below the current one in the parent menu..
[17:17] <bratsche> But there are two things that can keep it from becoming the active menuitem.. a timer, and this stay-up triangle.
[17:22] <bratsche> Anyway, we should think about this some.  Indicator icons are small enough that in the case of indicator-sound, going to all the trouble of duplicating this stay-up triangle might be more trouble than it's worth.  Judging by the screenshot in  qense's bug, the stay-up triangle would cover most the majority of the neighboring indicator icon anyway, so maybe a simple timer would be enough.
[18:22] <salty-horse> hello!
[18:23] <salty-horse> is there any reason why the icons in the indicator applet are so fat and spacious? they use a lot of whitespace around the icon, which causes big gaps between every two icons
[18:24] <salty-horse> also, the changes to gwibber's menu mean that if I don't like the indicator applet, I can't have a regular gwibber icon in the notifications area
[18:33] <qense> bratsche: I'll confirm the bug.
[20:04] <qense> tedg: Are you in Bug Control, or otherwise capable of viewing private bug reports?
[20:05] <tedg> qense: I used to be...
[20:05] <tedg> qense: Let's try one :)
[20:06] <qense> tedg: bug 541946 is a private
[20:06] <ubot4> qense: Bug 541946 on http://launchpad.net/bugs/541946 is private
[20:10] <qense> tedg: By the way, someone blogged against using GET_PRIVATE() methods, he says they are inefficient: http://blogs.gnome.org/jjardon/2010/03/30/improve-performance-use-priv-instead-get_priv-macros/
[20:10] <qense> tedg: Do you agree?
[20:11] <tedg> qense: Yeah, we've been slowly converting them.  I'm not sure it's enough to worry about though.
[20:11] <tedg> Yeah, I can see that bug.
[20:11] <qense> good
[20:11] <qense> I mentioned the GET_PRIVATE thing because there is a crash report in bug 545030 where indicator-application-service crashes on such a function.
[20:11] <ubot4> qense: Bug 545030 on http://launchpad.net/bugs/545030 is private
[20:14] <qense> tedg: and another crash also happens with a *priv that was obtained using GET_PRIVATE
[20:14] <qense> Could it be that the macro is a bit unreliable?
[20:16] <tedg> qense: It's not really as much a macro as it is a function call.
[20:16] <tedg> qense: Really, if the objects is there -- it shouldn't fail.
[20:17] <qense> tedg: So somehow the private object wasn't there during those crashes?
[20:18] <tedg> qense: The private section isn't an object really, it's just a memory region.
=== salty_horse is now known as salty-horse
[21:37] <funkyHat> Is there a plan to differentiate between new mail and new instant message in the messaging menu icon?
[21:39] <funkyHat> As it stands I either find myself often clicking the icon to see if it's an IM, only to be annoyed that it's only an email, or not clicking and then later finding I've missed an IM
[22:14] <vish> funkyHat: i'v been mentioning this since the beginning ;0  kinda pointless having an envelope for IM , mail , tweet and probably even rss o.0