Re: [Gtk-osx-devs] [python] Multiple python instances of gtk_osxapplication
- From: John Ralls <jralls ceridwen us>
- To: GTK+-2 OSX Devs <gtk-osx-devs lists sourceforge net>
- Subject: Re: [Gtk-osx-devs] [python] Multiple python instances of gtk_osxapplication
- Date: Mon, 9 Aug 2010 07:12:51 -0700
On Aug 8, 2010, at 9:14 PM, Richard Procter wrote:
>
> On 30/07/2010, at 2:59 AM, John Ralls wrote:
>
>>
>> On Jul 28, 2010, at 9:09 PM, Richard Procter wrote:
>>
>>> Hi there,
>>>
>>> A couple of days ago I tried instantiating two
>>> gtk_osxapplication.OSXApplication()s, which the source seems to
>>> suggest is ok (at least under C) as the underlying object is a
>>> singleton. This was to avoid coupling the highest level of my program
>>> with one of the lowest, which needs access to the bundle paths.
>>>
>>> Unfortunately it didn't work (I'm afraid I don't remember the
>>> details; if anyone is interested I can try to reproduce it).
>>>
>>
>> [snip]
>>
>> Please do see if you can reproduce the problem. It does need to be
>> fixed.
>
> Hi John,
>
> I had a chance to do this today, and it worked without issue as far
> as I could tell. It's certainly possible that it was an environmental
> problem at my end - sorry I can't be more categorical.
OK. Well, if it ever comes up again, let me know.
The next release, which I hope to get out today, will incorporate your changes to the bundle functions (with a slight twist for backwards compatibility and to make it obvious that they're not class functions: I renamed them to quartz_application_get_bundle() etc. and made the original names macros.) I also found where I'd gone astray in the constructor locking for GtkOSXApplication and fixed that, so it should now be thread-safe (though I haven't written a test to make sure).
Regards,
John Ralls
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]