Re: [us...@lists.monobjc.net] NSProxy exception

2010-01-07 Thread Laurent Etiemble
Hello, I have found a case that looks close to what you have reported: when a NSDistantObject instance gets deallocated, the bridge's lookup fails because the instance does not responds to "isKindOfClass:" selector. I have encountered it while working on the Growl Framework integration. I have be

Re: [us...@lists.monobjc.net] NSProxy exception

2009-12-10 Thread Duane Wandless
Making a test case is not easy. And this may actually be a SnowLeopard only issue. But I think I found the cause. I have a bunch of these: public NSString Name { [ObjectiveCMessage("name")] get { return new NSString("name");

Re: [us...@lists.monobjc.net] NSProxy exception

2009-11-25 Thread Laurent Etiemble
Hello, Can you post a small test-case so we can investigate the issue ? Regards, Laurent Etiemble. 2009/11/18 Duane Wandless : > I am getting the full call stack below when running, on SL and Leopard. > Using 2.4.2.3 and Monobjc 2.0.413.0.  Now I'm pretty confident this is a > terrible solution

[us...@lists.monobjc.net] NSProxy exception

2009-11-17 Thread Duane Wandless
I am getting the full call stack below when running, on SL and Leopard. Using 2.4.2.3 and Monobjc 2.0.413.0. Now I'm pretty confident this is a terrible solution I found. Any suggestions on how I can address this correctly would be greatly appreciated. I traced the workaround to NSProxy.Dealloc(