From: Antoine M. <an...@na...> - 2011-05-27 05:49:14
|
On 05/17/2011 10:03 PM, John Ralls wrote: > > On May 17, 2011, at 12:32 AM, Antoine Martin wrote: > >> On 05/12/2011 07:35 PM, John Ralls wrote: >>> >>> On May 12, 2011, at 5:43 AM, Antoine Martin wrote: >>> >>>> (snip) >>>>> I've attached my revised test-statusicon.py. Try it and see if you can get the "Icon Activated" message. >>>> I'll give it a go asap (a week or two). >> I couldn't get it to fire... I must have imagined it. >> >> >>>> >>>>> No, in bugzilla against Gtk. It's a gtk bug, not a gtk-osx bug. >>>> Found an existing bug so I added info there, looks like the same issue: >>>> https://bugzilla.gnome.org/show_bug.cgi?id=549153 >>> >>> Great, thanks. >> The suggested patch sounds like it should solve the problem: >> https://bugzilla.gnome.org/show_bug.cgi?id=549153#c12 >> But it doesn't seem to be making any difference for me. Can you double >> check? >> >> Is there any way we can force the application to become active when the >> status icon is clicked? Whatever currently makes >> NSApplicationDidBecomeActive fire? > > Can we keep the discussion about that on the bug? It's not really a gtk-osx issue, and AFAIK Paul doesn't read this list. Yes, sorry about that and about the delay for this response. I was just hoping that someone could confirm my findings before posting. (bug has now been updated) > As for getting the application to become active, the statusicon emits a POPUP_MENU_SIGNAL when it's clicked. > You can handle that anyway you like. Yes, I can do anything I like when I get the event, I just don't know what OSX api to call to make the application active. Cheers Antoine > > Regards, > John Ralls > |