Re: [Pyobjc-dev] Problem with PyObjc-1.1b2 and key value binding
Brought to you by:
ronaldoussoren
From: Ronald O. <ron...@ma...> - 2004-05-03 15:10:07
|
On 3-mei-04, at 16:12, Bob Ippolito wrote: > On May 3, 2004, at 5:52 AM, <mat...@da...> > wrote: > >> So I played around with KVB using PyObjc 1.0. Unfortunetely, it did >> not >> really work well (I ran into segmentation faults) , so I gave >> PyObjc-1.1b2 >> >> a try. The nasty segmentation faults went away and all seemed to work >> as >> expected, but now I've got problems with access to Objective-C >> variables >> (outlets in particular). The normal way, e.g. 'obj.outlet', does no >> longer >> >> work. Apparently as soon as some controller watches 'obj'. However, >> I >> can use PyObjCTools.KeyValueCoding.getKey to obtain access. > > Not bleeding edge enough. Key Value Observing was fixed post-1.1b2. > Please check out CVS HEAD and try that. > I hope cut the 1.1 release next weekend, I had planned to do that yesterday but ran into a problem on Jaguar :-( Ronald -- X|support bv http://www.xsupport.nl/ T: +31 610271479 F: +31 204416173 |