FROM : Jonathan Dann
DATE : Fri Jan 11 20:51:54 2008
On 11 Jan 2008, at 19:46, mmalc crawford wrote:
>
> On Jan 11, 2008, at 11:38 AM, Jonathan Dann wrote:
>
>> The @"value" is the binding name, not the key. The key is the name
>> of your instance variable you've bound to the NSTextField
>> NSString * newString // assume this exists
>> [aTextField setValue:newString forKey:@"personName"];
>> where personName is your ivar.
>>
> No. Don't do this. (a) It won't work. (b) This is not how
> bindings is designed to work.
> This is discussed in the documentation.
>
> mmalc
>
Yeah sorry, I'm too tired so I make embarrassing typos, the ivar in
you class should be updated programatically by
[self setValue:newString forKey:@"personName"];
or self.personName = newValue
from within your class
Jonathan
DATE : Fri Jan 11 20:51:54 2008
On 11 Jan 2008, at 19:46, mmalc crawford wrote:
>
> On Jan 11, 2008, at 11:38 AM, Jonathan Dann wrote:
>
>> The @"value" is the binding name, not the key. The key is the name
>> of your instance variable you've bound to the NSTextField
>> NSString * newString // assume this exists
>> [aTextField setValue:newString forKey:@"personName"];
>> where personName is your ivar.
>>
> No. Don't do this. (a) It won't work. (b) This is not how
> bindings is designed to work.
> This is discussed in the documentation.
>
> mmalc
>
Yeah sorry, I'm too tired so I make embarrassing typos, the ivar in
you class should be updated programatically by
[self setValue:newString forKey:@"personName"];
or self.personName = newValue
from within your class
Jonathan
| Related mails | Author | Date |
|---|---|---|
| Jonathan Dann | Jan 11, 20:38 | |
| mmalc crawford | Jan 11, 20:46 | |
| Jonathan Dann | Jan 11, 20:51 | |
| Damian Terentiev | Jan 11, 22:27 | |
| mmalc crawford | Jan 11, 22:43 |






Cocoa mail archive

