On 4 Dec 2011, at 23:09, Jens Alfke wrote:
>
>> *** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of class
>> (SplitsTestSet)
>>
>> I really don't understand why this is happening. I'm convinced it's
>> not a problem with library linking, as these apps have no problem
>> instan
A little earlier I wrote...
> The Trainer app is where things fall over. It reads the file into
> an NSData object and tries to decode it with NSKeyedUnarchiver's
> -unarchiveWithData: but this results in:
>
> *** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of class
> (Splits
I'm having a problem decoding a keyed archive, and I would appreciate
it if some kind soul here can swing the relevant clue bat...
My workspace contains three OS X projects:
* A static library: 'Splits Image Lib'. This contains, inter alia,
a class called SplitsTestSet, which conforms to NSCodi
On 18 Aug 2010, at 01:26, Shawn Erickson wrote:
>
> So in general you shouldn't worry about free RAM shrinking to a sliver
> of total system RAM over time... however if your application loads
> file data (aka image data in your case) only once or it is unlikely
> your application will load the sam
On 18 Aug 2010, at 06:57, Ken Ferry wrote:
>
> Did you say that the Object Alloc tool does not report the memory that is
> being used? First verify that. You don't want to use the object alloc tool
> from the leaks template, its config options are not appropriate. Start from
> the "Allocatio
On 18 Aug 2010, at 01:31, Ken Thomases wrote:
> On Aug 17, 2010, at 7:26 PM, Shawn Erickson wrote:
>
>> When you say "free" I assume you mean the "free:" number listed in
>> activity viewer for the system as a whole?
>
>> If so then what you are seeing is an expected result of the "unified
>> buf
On 18 Aug 2010, at 01:26, Shawn Erickson wrote:
>
> ... however if your application loads
> file data (aka image data in your case) only once or it is unlikely
> your application will load the same file data again in the reasonable
> near future then you should look at disabling file caching of th
On 17 Aug 2010, at 22:48, Sean McBride wrote:
> On Tue, 17 Aug 2010 22:20:55 +0100, Stuart Rogers said:
>
>>>> NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
>>>> ...
>>>> [pool release];
>>>
>>> Have you tried using
On 17 Aug 2010, at 21:36, Cem Karan wrote:
> On Aug 17, 2010, at 4:05 PM, Stuart Rogers wrote:
>>
>> NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
>> ...
>> [pool release];
>
> Have you tried using drain instead of release? That seems to be t
On 17 Aug 2010, at 18:07, Ken Ferry wrote:
> On Tue, Aug 17, 2010 at 9:53 AM, Cem Karan wrote:
>
>> One dumb question; I see where you're putting images into an autorelease
>> pool, but I don't see you setting up or tearing down pools. Where are you
>> doing that?
>
> Or, it could be much eas
On 17 Aug 2010, at 18:05, Ken Ferry wrote:
>
> (1) I would focus your attention on CoreImage in this case.
> (2) It is wonderful that you realized that if you want the bits in a specific
> pixel format then you need to draw them in a bitmap, but you now have a
> redundant bitmap:
Yes, I wanted
I'm having enormous difficulty keeping tabs on memory usage in my current
project. I'm happy that I'm not leaking anything - Build & Analyse reports no
issues, and neither does Instruments (Object Allocations and Leaks). And yet,
when watching bulk memory usage I see my free RAM dropping like a s
I have implemented -copyWithZone in my NSTFC subclass as such:
- (id)copyWithZone:(NSZone *)zone
{
MyTableCell*copy = [super copyWithZone:zone];
copy.cellObject = [self.cellObject copy];
copy.gridController = [self.ViewController copy];
return copy;
}
NSCells use NSCopyObject to do t
On 28 Sep 2008, at 10:02, Dave DeLong wrote:
I'm building an app, and I've got a bunch of interface object
definitions called "InputElements". There are a couple subclasses,
such as InputElementButton and InputElementSlider.
I'm building the interface via an "InputMode" object, that contains a
If I wanted to store an object in a dictionary and set its key as
the
object's memory address - how would I go about doing this?
I'm racking my brains trying to think of a good reason to do this
and am
drawing a blank. I can, however, think of myriad bad reasons.
Agreed - I can't help
David <[EMAIL PROTECTED]> wrote:
So, I'm realizing that maybe its more reasonable to back down to
just using a data source, target/action and delegates.
Don't think of it as backing down; think of it as using a more appropriate
technology. (For some appropriate definition of 'appropriate' of
16 matches
Mail list logo
