Re: [Pyobjc-dev] problems building editable tableviews

[Ronald O. <ous...@ci...>]

On Thursday, Oct 17, 2002, at 18:12 Europe/Amsterdam, Aaron Swartz 
wrote:

> Hi there,
>
> I've got a PyObjC app that has a table view working great, but as soon 
> as I add a definition for 
> tableView_setObjectValue_forTableColumn_row_, my app crashes as soon 
> as try to edit one of the rows and before my Python function gets 
> called. Here's the stacktrace:

Oops, you probably triggered a bug. Did you specify a signature for 
tableView_setObject*? (tableView_set* = selector(tableView_set*, 
signature="v@:@@@i"))

>
> Also, what's the policy on threading? I expect my app to do some 
> intense networking and indexing, and I don't want it to become 
> unresponsive while it's doing that. I tried importing "threading", but 
> when I tried to do something in another thread, it spewed out 
> thousands of no autoreleasepool -- leaking! messages.
>
Threading is not supported at the moment. If you create the thread 
using an Objective-C class (NSThread IIRC), the thread does not even 
have its own interpreter state (for the python interpreter); which will 
result in very interesting behaviour :-)

If you create the thread using the module 'thread' you might get 
working code if you create (and hang on to) an NSAutoreleasePool 
instance.

Ronald