Question

我有一个帮助类。

@interface CustomOnScreenshot : NSObject;

@property (copy) void (^finishedCallback)(id sender);

-(instancetype)initWithCallback: (void (^)(id sender))callback;

+(instancetype)onScreenshot:(void (^)(id sender))callback;

@end

@implementation CustomOnScreenshot

-(instancetype)initWithCallback: (void (^)(id sender))callback{
    self = [super init];
    if (self) {
        self.finishedCallback = callback;
        [self subscribeEvent];
    }
    return self;
}

+(instancetype)onScreenshot:(void (^)(id sender))callback{
    CustomOnScreenshot * onScreenShot = [self new];
    [onScreenShot setFinishedCallback:callback];
    return onScreenShot;
}

-(void)subscribeEvent{
    NSLog(@"CustomOnScreenshot subscribeEvent");
    [[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(doOnScreenShot:) name:UIApplicationUserDidTakeScreenshotNotification object:nil];
}

-(void)unsubscribeEvent{
    [[NSNotificationCenter defaultCenter] removeObserver:self name:UIApplicationUserDidTakeScreenshotNotification object:nil];
}

-(void)doOnScreenShot: (id)sender{
    if (self.finishedCallback) {
        self.finishedCallback(sender);
    }
}

-(void)dealloc{
    NSLog(@"CustomOnScreenshot dealloc");
    [self unsubscribeEvent];
}

问题在于，如果按预期使用它，则会立即销毁该对象

- (void)viewDidLoad {
    [super viewDidLoad];
    [CustomOnScreenshot onScreenshot:^(id sender) {
        // CUSTOM code
    }];
}

日志：
CustomOnScreenshot subscribeEvent
CustomOnScreenshot dealloc

只有当我在属性中使用结果时才会起作用，但我发现这个过多了

@property (strong, nonatomic) CustomOnScreenshot * customOnScreenshot;

- (void)viewDidLoad {
    [super viewDidLoad];
    self.customOnScreenshot = [CustomOnScreenshot onScreenshot:^(id sender) {
        // CUSTOM code
    }];
}

Answer 1

如果您没有 CustomOnScreenshot实例的强引用，那么只要+onScreenshot:完成执行，ARC就会释放该对象。

这就是@property修复它的原因。

如果您不想要@property，那么我建议使用单身人士。

初始化后销毁回调块的对象

1 个答案: