3

I have a UITableView that has cells containing text fields. As the user edits each text field, I need to keep track of the cell's text field value (even when the cell is no longer displayed, so simply tracking the text field does not work). So I used Key-Value Observing and set an observer for each text field in my UITableViewController subclass:

[cell addObserver:self forKeyPath:@"textField.text" options:NSKeyValueObservingOptionNew context:nil];

And save new changes to the text field in the class's observeValueForKeyPath:(NSString *)keyPath ofObject:(id)object change:(NSDictionary *)change context:(void *)context method.

This works great in iOS 6, but in iOS 7 KVO isn't called when the user changes the text field value. Apparently the setter method called by pressing "done" on the keyboard doesn't call KVO anymore.

Is there a workaround to this? Or a better way of listening for this change? I need to know what cell the text field belongs to, so implementing the text field's method editingDidEnd doesn't work for me.

Thanks in advance.

PerTaters
  • 33
  • 5

1 Answers1

1

I'm not sure about whether there is a workaround for this or not but there surely is a better way of listening for the UITextField text value. If you are creating instances of UITextField programmatically, all you need to do is add an event handler for them to notify your class about the text changing events. For example:

[myTextField addTarget:self action:@selector(editingChanged:) forControlEvents:UIControlEventEditingChanged];


- (void)editingChanged:(UITextField *)sender {
  NSString *targetText = sender.text;
}
Eugene
  • 10,006
  • 4
  • 37
  • 55
  • There is also a notification trigerred and also a delegate. – Sulthan Sep 19 '13 at 17:55
  • I thought about using this, but I need to know which cell the text field belongs to. On second thought though I realized I still use this, and just get that cell's indexPath using `NSIndexPath *indexPath = [[self.tableView indexPathsForRowsInRect:sender.frame] firstObject]` and from there get the cell with `[self.tableView cellForRowAtIndexPath:indexPath]`. Thank you! – PerTaters Sep 19 '13 at 18:10
  • I've created a subclass that exposes an "observableText" property using Eugene's approach. The reason for this change in iOS 7 is that UITextField uses 2 subviews (placeholder and actual text field) and its own text property is just a proxy – Martin Ullrich Dec 17 '13 at 21:32