Thanks Fred,
It looks like that has fixed the problem with NSApp. It also appears to have
solved the other problem that I reported to you privately. We will do some more
testing and let you know if we run into any other problems with nib loading.
Thanks for the quick fix!
Regards,
Doug
On Ma
Thank you for pointing out the problem with NSApp. This was caused by a
missing retain in some part of GSNibLoading that I hadn't cleaned up.
Hopefully this is fixed now. If there are any other issues I hope we can
resolve them as quick as that one.
Fred
Am 22.03.2010 18:24, schrieb Doug Simons:
I'm not positive, but I'm guessing that these nib loading changes checked in
over the weekend are the cause of new crashes that we are seeing when building
with the latest code (r30018) on Windows.
Our app now crashes on launch. Here's the relevant gdb output:
Program received signal SIGSEGV, S
Hi Fred!
Am 19.03.2010 09:20, schrieb Fred Kiefer:
My current position on NIB loading is that no magic should happen
there.
Objects created while loading a NIB file should follow the standard
rules. Nothing will be retained except for the top level objects
being
retained in the top level ob
Am 19.03.2010 09:20, schrieb Fred Kiefer:
> My current position on NIB loading is that no magic should happen there.
> Objects created while loading a NIB file should follow the standard
> rules. Nothing will be retained except for the top level objects being
> retained in the top level object arra
