Hi, I am developing an application where I need to be able to handle the
following requirements:
- Deployment: MacOS X 10.6 and later. May want to develop an iPad version later.
- Type of application: Display and manipulation of graphical objects on a
canvas.
- Number of graphical objects: up t
I seem to have hit a few limitations with ARC.
1.) Subclasses of CALayer are not being fully released which causes my view
controller to remain around. There is still some small bit of memory being left
behind. Even if I do the following simple code:
-(void) viewDidLoad {
[super viewDidL
It sounds, though, as if it should be ok to use
observeValueForKeyPath:ofObject:change:context (which will run on the secondary
thread, by the sound of it) as a way of monitoring the fact that "something"
has changed in the state of my object. I can then use that as a single place in
which I sc
Could you post the code for the sublayer and what is the residual memory?
On Sat, Mar 24, 2012 at 4:17 AM, Scott Andrew wrote:
> I seem to have hit a few limitations with ARC.
>
> 1.) Subclasses of CALayer are not being fully released which causes my
> view controller to remain around. There is st
Hi Jonathan,
Yes, that would work as long as the thing that changed is KVO compliant. To
update the shadow object, you can do as Jens suggested, or use dispatch_async
to the main thread, or use the main operation queue as described in the
receptionist pattern.
Cheers,
Dave
On 2012-03-24, at 5:
On Mar 24, 2012, at 2:46 AM, Jonathan Taylor wrote:
> It sounds, though, as if it should be ok to use
> observeValueForKeyPath:ofObject:change:context (which will run on the
> secondary thread, by the sound of it) as a way of monitoring the fact that
> "something" has changed in the state of m
On Mar 24, 2012, at 10:46 AM, Jonathan Taylor wrote:
It sounds, though, as if it should be ok to use
observeValueForKeyPath:ofObject:change:context (which will run on
the secondary thread, by the sound of it) as a way of monitoring the
fact that "something" has changed in the state of my o
Scott,
Please reduce this down to a test case so that we might try and reproduce what
you are observing.
Thanks!
davez
On Mar 24, 2012, at 1:17 AM, Scott Andrew wrote:
> I seem to have hit a few limitations with ARC.
>
> 1.) Subclasses of CALayer are not being fully released which causes m
Can anyone explain what is going on here:
NSDate *now = [NSDate date];
NSLog(@"now is %@", now);
NSDateFormatter *dateFormatter = [[NSDateFormatter alloc] init];
[dateFormatter setTimeZone:[NSTimeZone localTimeZone]]; // this is MDT
for me
[dateFormatter s
Donald Hall wrote:
2012-03-24 20:57:18.976 calendardatetest[77052:707] now is 2012-03-25 02:57:18
+
2012-03-24 20:57:18.977 calendardatetest[77052:707] stringFromDate=8:57 PM
2012-03-24 20:57:18.978 calendardatetest[77052:707] new date from
string=1970-01-02 03:57:00 +
2012-03-24 20:57:
On Mar 25, 2012, at 11:14 AM, Donald Hall wrote:
> Can anyone explain what is going on here:
>
>NSDate *now = [NSDate date];
>NSLog(@"now is %@", now);
>
>NSDateFormatter *dateFormatter = [[NSDateFormatter alloc] init];
>[dateFormatter setTimeZone:[NSTimeZone loc
11 matches
Mail list logo
