Re: [gtk-osx-users] when to call gtkosx_application_ready() in an application that initializes in an idle callback

2013-06-15 Thread John Ralls
On Jun 14, 2013, at 10:46 PM, Richard Procter richard.n.proc...@gmail.com wrote: On 15/06/2013, at 12:53 PM, John Ralls wrote: So my guess is that this delegate isn't registered until gtkosx_application_ready() is called. However, checking this by the code I get muddled, as this

Re: [gtk-osx-users] when to call gtkosx_application_ready() in an application that initializes in an idle callback

2013-06-14 Thread Olivier Sessink
On 06/14/2013 05:27 AM, John Ralls wrote: On Jun 13, 2013, at 4:36 PM, Olivier Sessink oliviersess...@gmail.com wrote: Hi all, we're currently working to fix some issues with Bluefish on OSX. Bluefish initializes the GUI in an idle callback. So gtk_main() is called very early (before

Re: [gtk-osx-users] when to call gtkosx_application_ready() in an application that initializes in an idle callback

2013-06-14 Thread Richard Procter
Hi Olivier, On 15/06/2013, at 7:51 AM, Olivier Sessink wrote: various other initialization parts of Bluefish use multiple threads, and use the main loop to sync the results. If we don't run the first initialization inside gtk_main all the threads have to wait for the gui to be finished

Re: [gtk-osx-users] when to call gtkosx_application_ready() in an application that initializes in an idle callback

2013-06-14 Thread Richard Procter
On 15/06/2013, at 12:53 PM, John Ralls wrote: So my guess is that this delegate isn't registered until gtkosx_application_ready() is called. However, checking this by the code I get muddled, as this object is only created in static void gtkosx_application_init, which is never called in