Re: IB 3.1 breaks NSCollectionView bindings?
Re: IB 3.1 breaks NSCollectionView bindings?
- Subject: Re: IB 3.1 breaks NSCollectionView bindings?
- From: Gerd Knops <email@hidden>
- Date: Wed, 30 Jul 2008 11:53:02 -0500
On Jul 29, 2008, at 8:18 PM, Jonathan Hess wrote:
Hey Gerd -
When IB saves a NIB, or compiles a XIB to a NIB, the bindings are
generated in an indeterministic order.
Which seems to be the cause. The only meaningful difference between a
non-working and a working xib is the location of a single binding.
Interestingly the location of that binding in the xib seems to make a
difference for several other bindings as well.
The most likely explanation for the behavior you are seeing is that
you're app is either not actually implementing KVO compliance for
one of the keys, or is sensitive to the order that the bindings are
established.
Definitely not the case.
For example one of the bindings is to the Collection View Item
"selected" property (the NSCollectionView selectionIndexes are bound
to a stock array controller). Depending on the placement of the above
mentioned (and unrelated) binding, the "selected" binding works or
does not.
Even more puzzling is that for the failing bindings I debugged it
seems the setters are called, but the getters are not.
I am guessing that something changed with one of the recent updates
(be it IB 3.1 or OS X 10.5.4) that causes the quirky internal setup
(awake) of NSCollectionView to fail depending on the order in which
bindings are stored in the xib.
Needless to say it is extremely frustrating to make a simple change
like change the position by a UI element by a pixel, only to find that
most of the interface mysteriously fails afterwards. And more
frustrating that the only recourse seems to be to make random changes
until everything works again...
See rdar://problem/6109341
Gerd
Jon Hess
On Jul 29, 2008, at 5:30 PM, Gerd Knops wrote:
New with IB 3.1:
When saving xib's containing a NSCollectionView, the various
bindings sometimes work and sometimes don't. When they don't work,
deleting them and replacing them with the exact same values, or
just changing a (unused) flag might fix it, but the next time saved
(even after a simply geometry adjustment) bindings might be broken
again.
Anybody else seing this? Driving me crazy!
Gerd
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden