On Dec 14, 2009, at 12:16 PM, Matthew Lindfield Seager wrote:
> That belongs to the preceding LSTypeIsPackage key.
Yea, I was still sleeping when I responded to that last post. ;) Turned out
that resource CFBundleDisplayName/CFBundleDocumentTypes should not have even
been in the plist file
Not directly related to your problem but just for your info...
On Tuesday, December 15, 2009, Joe The Programmer
wrote:
>Regardless, there seems to be an erroneous in there.
That belongs to the preceding LSTypeIsPackage key.
___
Cocoa-dev mailing li
And indeed, your plist is broken. CFBundleDisplayName should be a string not
an array. It seems that what is "CFBundleDisplayName" should be
"CFBundleDocumentTypes".
--
Julien
On Mon, Dec 14, 2009 at 3:29 PM, Joe The Programmer <
joetheappleprogram...@gmail.com> wrote:
>
> On Dec 14, 2009, at 4
On 13 dec 2009, at 23.06, Joar Wingfors wrote:
>> Two occurrences of the following massage are appearing in the console:
>> -[NSCFArray _getCString:maxLength:encoding:]: unrecognized selector sent to
>> instance 0x4016e0
>
> That's almost certainly an indication of a memory management error in
On Dec 14, 2009, at 4:28 AM, Julien Jalon wrote:
> It's not necessarily a memory management problem. As this happens very early
> in the application launch, when Launch Services uses your Info.plist to
> register the application, your problem might also be that an entry supposed
> to be a stri
It's not necessarily a memory management problem. As this happens very early
in the application launch, when Launch Services uses your Info.plist to
register the application, your problem might also be that an entry supposed
to be a string is in fact an array.
On Mon, Dec 14, 2009 at 9:09 AM, Joe
On Dec 14, 2009, at 12:52 AM, Kyle Sluder wrote:
> Turning on GC is not the solution to your problem. Fixing your memory
> management bugs is the solution.
On Dec 14, 2009, at 12:54 AM, Joar Wingfors wrote:
> For a trivial app it might be. For anything else, it would not be. GC and RC
> are fu
On 13 dec 2009, at 23.44, Joe The Programmer wrote:
> Is GC as easy to implement as toggling the GCC_ENABLE_OBJC_GC build setting
> to either supported or required?
For a trivial app it might be. For anything else, it would not be. GC and RC
are fundamentally different memory management model
On Sun, Dec 13, 2009 at 11:44 PM, Joe The Programmer
wrote:
> Great, thanks. Garbage Collection is not currently being used. This code
> previously was built with the 10.4 SDK which did not support GC. Now it
> builds with the 10.5 SDK, so I would assume is GC capable.
Turning on GC is not t
On Dec 14, 2009, at 12:06 AM, Joar Wingfors wrote:
> That's almost certainly an indication of a memory management error in your
> application. If you're not using Garbage Collection in your app, I'd suggest
> that you troubleshoot this using zombies. Search for "NSZombieEnabled" to
> find help
On 13 dec 2009, at 22.26, Joe Programmer wrote:
> Two occurrences of the following massage are appearing in the console:
> -[NSCFArray _getCString:maxLength:encoding:]: unrecognized selector sent to
> instance 0x4016e0
That's almost certainly an indication of a memory management error in your
11 matches
Mail list logo
