[00:43] <foo123> is the C/C++ interface for libindicator more stable than the python one?
[01:04] <foo123> hello?
[01:08] <RAOF> foo123: Probably a bit late for most of the members of this channel.
[01:09] <RAOF> And what do you mean by “stable” in this instance (it's got multiple distinct meanings, sadly)
[01:09] <foo123> submenus have a reversed order
[01:10] <foo123> it flickers badly
[01:10] <foo123> I can't seem to get any signal that would indicate if the menu is visible
[01:11] <foo123> topic_menu_item.set_state(gtk.STATE_INSENSITIVE) makes the item insensitive
[01:13] <foo123> but I can't set it back
[01:14] <RAOF> I'm not sure about that.
[01:15] <RAOF> So, you're using the “does what the API docs describe” meaning of “stability”, then :)
[01:16] <foo123> set_state(gtk.STATE_NORMAL) does not make it senstive again
[01:17] <foo123> but .set_sensitive(True) works go figure
[01:18] <foo123> the big problem is I don't seem to get any events except the 4 useless appindicator events and the menu "activated" one
[01:20] <foo123> and that if I make a menu a submenu the items are ordered from bottom to top but if I make it a regular menu it is ordered correctly... WHY?!?!
[02:34] <foo123> anyone know anything about indicators?
[02:44] <nigelb> !ask | foo123
[02:44] <ubot5> foo123: Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)
[03:25] <foo123> I already asked my question ...
[03:30] <RAOF> foo123: Describing what you're actually trying to do will probably result in a better class of response.
[03:30] <RAOF> Although, again, that response is likely to require waiting until the ayatana people are actually awake :)
[03:33] <foo123> no problem, what time is usually good?
[03:35] <RAOF> UK working hours are generally good.
[03:37] <RAOF> (So, in around 8 hours) :)
[03:38] <RAOF> But, although I'm not particularly familiar with the details of appindicators, it sounds to me like you're possibly trying to do something they're not designed for.
[09:40] <Cimi> hi chaotic
[10:15] <chaotic> Cimi: morning
[10:15] <Cimi> skype man? :)
[10:16] <Cimi> chaotic ^^
[10:17] <chaotic> Cimi: just got a few things I need to do quickly - I'll get hold of you in about 10 mins if that's ok
[10:17] <Cimi> cool
[10:17] <Cimi> I'll wait
[10:33] <Cimi> as always, ott's minutes last twice :))
[10:38] <klattimer> Cimi: I'm really enjoying your new theme
[10:38] <klattimer> keep up the good work :)
[10:39] <Cimi> thanks karl
[10:53] <chaotic> Cimi: actually they last 4 times longer :)
[10:53] <chaotic> Cimi: be there soon
[10:53] <Cimi> ok
=== MacSlow is now known as MacSlow|lunch
[12:25] <klattimer> mpt, seb128 I've just sent you an email regarding the gsd indicator
[12:26] <klattimer> mpt I hope this makes you a little happier with them :)
=== MacSlow|lunch is now known as MacSlow
[13:13] <JanCBorchardt> vish, just saw that you assigned a bug from papercuts to null, should we do that with bugs that are not relevant to papercuts? (this seems to be the only way to unsubscribe papercutters)
[13:22] <vish> JanCBorchardt: yeah, if they are not ppc just switch them over to null
[13:23] <vish> JanCBorchardt: we get enough mails already ;)
[13:23] <JanCBorchardt> vish, cool, I searched for a way to do that just the other day ;)
[13:25] <vish> JanCBorchardt: usually if bug was reported only in ppc, i switch it over to the relevant bug task, if the relevant bug task is already there it goes to null
[13:28] <JanCBorchardt> vish, yep, thanks. I accidentally didn’t switch over then but made it to affect the other project as well.
[13:32] <JanCBorchardt> vish, oh and have you thought about the redirection after unmount thing?
[14:01] <JanCBorchardt> vish, and I just saw that you already nulled the copy-paste bug in the past to no avail ;)
[14:51] <klattimer> mpt: I'd like your comment on this; https://bugs.launchpad.net/ayatana-ubuntu/+bug/620331
[14:51] <ubot5> Launchpad bug 620331 in gnome-settings-daemon (Ubuntu) "please drop icon from keyboard indicator (affected: 1, heat: 10)" [Low,In progress]
[14:51] <mpt> klattimer, sent
[15:07] <klattimer> mpt: replied to you and cc'd mark and tedg as mark's been following this one
[15:07] <klattimer> thing is, we can probably produce all the icons we need now, and use them
[15:08] <klattimer> would be good if ivanka or davidbarth could look into getting the art done
[15:21] <bcurtiswx> hey all, idk if this is a indicator or gwibber issue, but when I'm actively viewing gwibber, why are entries for @replies still showing up in the indicator-me ?
[15:23] <bcurtiswx> i.e i see an @reply visually on gwibber, and it still shows an entry in indicator-me
[15:23] <bcurtiswx> the applet. sorry
[15:42] <foo123> Is the C indicator API less broken than the python one? Right now I have a few issues. My app does not receive signals, underlines are not usable as menu labels, submenus have a reversed order, and the menu items flicker when they are updated. Not to mention to disintuitiveness of "remove from panel" when you right click on the icon
[15:45] <klattimer> foo123: I have the signals problem with ibus
[15:46] <klattimer> if you hang on a tick I'll find you the bug number so you can add your comment
[15:46] <klattimer> https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/564034
[15:46] <ubot5> Error: Could not parse data returned by Launchpad: list.index(x): x not in list (https://launchpad.net/bugs/564034)
[15:46] <klattimer> there you go
[15:48] <foo123> The qustion is should I bother rewriting my indicator in C or should I give up on indicators and go back to implementing it as a panel applet
=== JanC_ is now known as JanC
[16:15] <klattimer> foo123: definitely stick to the indicators
[16:16] <klattimer> tedg: is probably working on the bugs in the python bindings
[16:18] <foo123> I am getting the impression that the bugs are not being fixed for 10.04 LTS
[16:21] <klattimer> foo123: you'd have to ask tedg about that
[16:22] <klattimer> I know sense has fixed one of the bugs you talked about
[16:22] <klattimer> or maybe the same bug, dunno https://bugs.launchpad.net/indicator-application/+bug/608219
[16:22] <ubot5> Launchpad bug 608219 in Application Indicators "Submenus not added when done so with Glade (affected: 1, heat: 103)" [Undecided,In progress]
[16:55] <tedg> foo123, It's hard to get things backported, but if there is a bug, I have no issue trying to help.
[16:55] <tedg> foo123, Sorry, I was in a meeting.
[17:07] <foo123> I'm trying to figure out what I should do from a LTS standpoint
[17:08] <foo123> I think it might be better for me to wait for the next LTS release at this point
[17:09] <foo123> I need the signals problem fixed so that I can get dynamic menus to work without consuming cpu while unused and to keep it from flickering
[17:10] <foo123> I dont know if the submenus being in reverse order is apython thing or not
[17:11] <foo123> and the underline bug #611943 is something I need fixed
[17:11] <ubot5> Launchpad bug 611943 in Application Indicators "menu items don't respect set_use_underline (affected: 1, heat: 10)" [Undecided,New] https://launchpad.net/bugs/611943
[17:13] <foo123> If these can't get fixed for lucid I'll need to go back to regular applets until the next LTS
=== mpt_ is now known as mpt
=== lamalex__ is now known as lamalex