قالب وردپرس درنا توس
Home / IOS Development / Bizarre problem with Property Observer: iOSProgramming

Bizarre problem with Property Observer: iOSProgramming



I only tracked an error that apparently came from nowhere – the code ran well earlier, and other similar situations do not give the same behavior.

I have a UITableViewCell with two public properties. Each is responsible for updating user interface components upon receiving data. In each case, the didSet property observer contains a feature that takes an argument from the property itself. In one case, while the observed observer burns exactly once, the feature burning it performs hundreds of times before crashing not only burns my application, but Xcode.

For reference, I code in 4.2 using v10.1. The error I received (when I see an error at all) has either been EXC_BAD_ACCESS or & # 39; Use of Black Type: Objective-C & # 39 ;. The fixation was to move the contents of the property observer's function directly into the property observer himself.

I have attempted to reproduce this behavior in other areas, including UITableViewCell's other property, and cannot. Should I avoid performing functions in real estate observers who take an argument from the property itself? Are these just ticking time bombs throughout my application? Or is this a mistake I, for a change, have nothing to do with?


Source link