Re: Order of instantiation within a NIB

FROM : John Brownlow
DATE : Wed Apr 13 00:02:59 2005

right. there you are. there are circumstances when you know which
object you want to be selected but not its index in the array. This is
likely to be rather a common situation after April 29. I suppose there
are reasons for not exposing 'selectedObjects' but it's annoying. In my
case I wanted to directly bind a constantly changing attribute of the
text at the insertion point to the visible selection in a table,
without having to delve into the table and find the index for every
iteration.

On Apr 12, 2005, at 5:51 PM, mmalcolm crawford wrote:

> On Apr 12, 2005, at 11:46 AM, John Brownlow wrote:
>

>> This is from memory, but I think I was trying to bind the
>> 'selectedObjects' key of an NSArrayController, which for some reason
>> does not appear to be exposed in Interface Builder. Anyway it was
>> something like that. There is at least one of the selection keys
>> which is annoyingly not exposed.
>>

> 'selectedObjects' isn't an exposed binding for an array controller. 
> The "official" exposed bindings are (IIRC):
>
>    editable,
>    contentArray,
>    contentArrayForMultipleSelection,
>    contentObject,
>    sortDescriptors,
>    selectionIndexes
>
> mmalc


--
John Brownlow
Deep Fried Films, Inc

http://www.johnbrownlow.com
http://www.pinkheadedbug.com