My IKImageBrowserView bound to an ArrayController is now spitting out
this error when the program launches
--ImageKit Error: reloadData called in non main thread
When I unbind it the error goes away along with the content no longer
being displayed. Any idea what could cause this?
Adam
On Sat,
I know its a hybrid approach, but the upside is I did not have to call
reloadData. As soon as I added an object to the arraycontroller it
became available in the view.
Adam
On Sat, Apr 5, 2008 at 12:28 AM, Steve Weller <[EMAIL PROTECTED]> wrote:
>
> On Apr 4, 2008, at 2:18 PM, Adam Gerson wrote
On Apr 4, 2008, at 2:18 PM, Adam Gerson wrote:
It does work. I have defined a core data entity that conforms to
IKBrowerItem protocol and my IKImageBrowserView is working with
bindings. I think you still need to point the delegate and data source
outlets to an object that implements the datasour
It does work. I have defined a core data entity that conforms to
IKBrowerItem protocol and my IKImageBrowserView is working with
bindings. I think you still need to point the delegate and data source
outlets to an object that implements the datasource methods:
//
I am attempting to use bindings to supply an IKImageBrowserView with
data. I have successfully used IKImageBrowserView with a data source,
but cannot get bindings to work. Should it work with bindings?
The array controller's contentArray is hooked up to an NSMutableArray
called storedImag
