Re: Making a Window Class Invocable from Any Thread

2008-11-05 Thread Hal Mueller
The "Late Night Cocoa" podcast episode on concurrent programming is very helpful too--especially if you have seen the concepts in operating system theory, but want a reminder of which Cocoa classes correspond to those concepts. http://www.mac-developer-network.com/podcasts/latenightcocoa/ep

Re: Making a Window Class Invocable from Any Thread

2008-11-05 Thread Jerry Krinock
On 2008 Nov, 04, at 22:29, Chris Hanson wrote: I'd actually caution you against this. Keep your processing distinct from your user interface, don't mix the two. Use some form of intermediate "status" object to pass information back to your main thread for presentation to the user, rather

Re: Making a Window Class Invocable from Any Thread

2008-11-04 Thread Chris Hanson
On Nov 4, 2008, at 2:22 PM, Jerry Krinock wrote: I have a class which programatically creates and manipulates an alert window, like NSAlert except it's capable of much more. It exposes about 55 methods, doing stuff like like -setTitle:, - setButtonTitle:, -setProgressAmount:, -removeAllSubv

Re: Making a Window Class Invocable from Any Thread

2008-11-04 Thread Michael Ash
On Tue, Nov 4, 2008 at 6:10 PM, Charles Steinman <[EMAIL PROTECTED]> wrote: > This sounds like it might be a good case for a proxy. You could create a > small class that looks something like this: > > @implementation MyClass > @synthesize targetWindow; > - (void)forwardInvocation:(NSInvocation *)i

Re: Making a Window Class Invocable from Any Thread

2008-11-04 Thread Charles Steinman
inock <[EMAIL PROTECTED]> > To: Cocoa Developers > Sent: Tuesday, November 4, 2008 2:22:35 PM > Subject: Making a Window Class Invocable from Any Thread > > I have a class which programatically creates and manipulates an alert > window, like NSAlert except it's capa

Re: Making a Window Class Invocable from Any Thread

2008-11-04 Thread Nick Zitzmann
On Nov 4, 2008, at 3:22 PM, Jerry Krinock wrote: This seems like a good solution but before I write wrappers for 55 methods I was wondering if anyone knows a better approach to this problem. Did you see the easy-to-miss NSInvocationOperation class? Nick Zitzmann

Making a Window Class Invocable from Any Thread

2008-11-04 Thread Jerry Krinock
I have a class which programatically creates and manipulates an alert window, like NSAlert except it's capable of much more. It exposes about 55 methods, doing stuff like like -setTitle:, -setButtonTitle:, - setProgressAmount:, -removeAllSubviews, -setPopupTitles:, setIconStyle: etc., etc.