Re: Tracking down source of [_NSControllerObjectProxy copyWithZone:]… error

2015-09-19 Thread Quincey Morris
On Sep 19, 2015, at 20:09 , Alex Hall wrote: > > [_NSControllerObjectProxy copyWithZone:]: unrecognized selector sent to > instance 0x60800ae0 > > failed to set (contentViewController) user defined inspected property on > (NSWindow): -[_NSControllerObjectProxy copyWithZone:]: unrecognized

Tracking down source of [_NSControllerObjectProxy copyWithZone:]… error

2015-09-19 Thread Alex Hall
Hey list, A binding is driving my app (my actual one, not the test one) and has been for days now--awesome! Amid more refactoring of my code, and adding a second binding which didn't take because of uninitialized properties, I've now started seeing this error in my debug log: [_NSControllerObje

Re: Generics Problem

2015-09-19 Thread Michael de Haan 
> On Sep 19, 2015, at 1:46 PM, Jens Alfke wrote: > > >> On Sep 19, 2015, at 11:26 AM, Quincey Morris >> > > wrote: >> >> It looks like Swift is incapable of resolving the specialization of U when >> there is more than one generic type specifier: >

Re: Generics Problem

2015-09-19 Thread Jonathan Hull
If you only need U to be a String or a Double, have you tried using a protocol instead (and then having both String & Double adhere to it). It doesn’t explain the compiler error, but it might work. I would also recommend using as? instead of as! here. Thanks, Jon > On Sep 19, 2015, at 10:54

Re: Generics Problem

2015-09-19 Thread Quincey Morris
On Sep 19, 2015, at 13:46 , Jens Alfke wrote: > > Maybe it’s because the second type-spec T isn’t defined when the function is > called. What you say sounds very plausible for my cut-down example, but unless I’m dreaming the original example explicitly declares what T is in the result type (E

Re: Generics Problem

2015-09-19 Thread Jens Alfke
> On Sep 19, 2015, at 11:26 AM, Quincey Morris > wrote: > > It looks like Swift is incapable of resolving the specialization of U when > there is more than one generic type specifier: Maybe it’s because the second type-spec T isn’t defined when the function is called. In both Michael’s and y

Re: Generics Problem

2015-09-19 Thread Quincey Morris
On Sep 19, 2015, at 10:54 , Michael de Haan  wrote: > > func createMOforEntityName(entityName:String, > context:NSManagedObjectContext, key:String, keyAttribute: U) -> (Bool, T) { > >guard let mo:T = self.moExistsWith(entityName, key:key, keyAttribute: > keyAttribute) else { It look

Generics Problem

2015-09-19 Thread Michael de Haan 
I am calling this function, func createMOforEntityName(entityName:String, context:NSManagedObjectContext, key:String, keyAttribute: U) -> (Bool, T) { guard let mo:T = self.moExistsWith(entityName, key:key, keyAttribute: keyAttribute) else { let mo:T =

Slow Keyboard in iOS 9.0

2015-09-19 Thread Gerriet M. Denkmann
Master-Detail app for iPhone Master has a TableView with words and a SearchField. DetailView has info about selected word. Hitting the Back-Button in the DetailView shows the MasterView and then (after what feels like a second) the Keyboard slides up. This is not what I want. Before iOS 9.0 the