Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-28 Thread John Love
(1) warning: no doSheetSelection:contextInfo method found which, I think, is due to the fact that the external class of mFileSheetDelegate = FileController, yet when referenced in SaveSheetController, it's = id, a general pointer. But, I thought all anonymous pointers were resolved at

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-27 Thread John Love
Graham, Yup, Nathan the double indirection of id * 1st, just the key snippet from FileController.m: @implementation FileController id mFileSheetDelegate; = Here's the complete interface and implementation files for just one SheetController, which has 2 buttons in its sheet window: //

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-27 Thread Graham Cox
On 28 Jun 2008, at 12:38 am, John Love wrote: [code snipped] Finally, you nailed it, almost (one small bug, see below). Phew! Okay ... all the snippets are done ... now, the questions: (1) warning: no doSheetSelection:contextInfo method found which, I think, is due to the

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-26 Thread John Love
Graham, Still pouring over your thesis .. in process, so let me ask just one thing at a time, rather than chew here on the whole thing. (1) learning about anonymous type = (id) .. I make this call within FC: [iboCalculateSheetCtrl showSheetOnParentWindow:itsWindow

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-26 Thread Nathan Kinsinger
On Jun 26, 2008, at 8:19 AM, John Love wrote: @implementation CalculateSheetController id *mFileSheetDelegate; id is already typed as a pointer, no need to add another level of indirection here. --Nathan ___ Cocoa-dev mailing list

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-26 Thread Graham Cox
On 27 Jun 2008, at 12:19 am, John Love wrote: Still pouring over your thesis I thought it was getting a bit damp around here... ;-) and at the very top: @implementation CalculateSheetController id *mFileSheetDelegate; Within the implementation of showSheetOnParentWindow, I get

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-19 Thread John Love
Completed the housekeeping I needed to do .. so I began moving all the sheet code over to SheetController. Within FileController, I have 3 IBOutlets which are the 3 different sheet NSWindow's *and* the same 3 sheet NSWindow outlets for SheetController. I need to pass the specific sheet to my

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-17 Thread John Love
I have your previous message typed out and I really have read it ... and I will re-read it and re-read until it clicks. You know how I feel about compartmentalization. I really don't want to abandon it because compartmentalization does work for me for the NSProgressIndicator that I have, as well

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-16 Thread John Love
Hello, Graham ... Because I have multiple calls to show a sheet, from various parts of my FileController, and because I wanted to make my sheet calls as general as possible, I really .. really .. wanted to have a distinct SheetController. As a result, I made calls from FileController to look

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-16 Thread Graham Cox
Hi John, Did you even read my last email? I hope so because I really spent a long time writing it. It may not have been clear, but I did my best! A separate SheetController *is* the right way to do it, but the way you are partitioning the responsibilities between your various controllers

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-12 Thread Graham Cox
Hi John, I hope you don't mind me cc'ing this to the list - I think it might be helpful to others (if not, my apologies for the noise). On 12 Jun 2008, at 9:43 pm, John Love wrote: Hi, Graham ... Graham, this is a condensed summary of my initial communication: Call it my fetish or

Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-10 Thread John Love
to shorten it. My app is a Cocoa Document based app. I have chosen the title Prevent Asynchronous operation of beginSheetModalForWindow because I use various calls to beginSheetModalForWindow in many parts of my app code and in one case I need the calls to didEndSelector to be completed *before* the code

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-10 Thread Michael Ash
On Tue, Jun 10, 2008 at 1:10 PM, John Love [EMAIL PROTECTED] wrote: I have chosen the title Prevent Asynchronous operation of beginSheetModalForWindow because I use various calls to beginSheetModalForWindow in many parts of my app code and in one case I need the calls to didEndSelector

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-10 Thread Jens Alfke
On 10 Jun '08, at 1:27 PM, Michael Ash wrote: If there were a synchronous API the code would have to somehow jump down the stack to where you're waiting for A, while somehow leaving the stuff that's waiting for B live farther up the stack. This is quite simply impossible in a C-based language.

Re: Prevent Asynchronous operation of beginSheetModalForWindow

2008-06-10 Thread Graham Cox
it. My app is a Cocoa Document based app. I have chosen the title Prevent Asynchronous operation of beginSheetModalForWindow because I use various calls to beginSheetModalForWindow in many parts of my app code and in one case I need the calls to didEndSelector to be completed *before* the code