On 07/02/2010, at 5:19 PM, Trygve Inda wrote:
> Would you instantiate the (very simple) NSWindowController subclass
> (CheckSheetController) in the nib, or just dynamically create it as needed?
> Obviously the window would exist in the nib but TableController could have
> an outlet to the window
>
> On 07/02/2010, at 5:05 PM, Trygve Inda wrote:
>
>> I think a sheet would work just as well... In either case the columns will
>> not adjust until the use clicks OK.
>>
>> My thought was to bind the checkboxes to BOOLs in a MutableDict within the
>> TableController. Once the sheet is dismisse
On 07/02/2010, at 5:05 PM, Trygve Inda wrote:
> I think a sheet would work just as well... In either case the columns will
> not adjust until the use clicks OK.
>
> My thought was to bind the checkboxes to BOOLs in a MutableDict within the
> TableController. Once the sheet is dismissed, I would
>> So it's window controller would just be a plain NSWindowController (no
>> subclass) and in my TableController id just do:
>>
>> returnCode = [NSApp runModalForWindow:[theWindController window]];
>
> It might or might not be a plain NSWindowController. Given the situation you
> described, it s
On 07/02/2010, at 4:33 PM, Trygve Inda wrote:
> I haven't really done a project quite like this before and in the past I
> have used a separate nib for each window.
A separate nib for every distinct window is a good idea. But often a sheet is
an auxiliary to some other more important window -
> 2010/2/6 Trygve Inda :
>> Any thoughts on a design pattern for this situation?
>
> I'd make your table view controller a subclass of NSViewController,
> and instead of using a modal window I'd use a sheet, which your table
> view controller would be the delegate of. All your logic gets to stay
>
>
> On 07/02/2010, at 3:52 PM, Trygve Inda wrote:
>
>> The checkboxes window is in is own nib
> []
>
>> Any drawback to this?
>>
>> It seems like overkill to create a custom class to manage the checkbox
>> window when all the checkboxes are controlled by bindings and there is only
>> an OK/Canc
2010/2/6 Trygve Inda :
> Any thoughts on a design pattern for this situation?
I'd make your table view controller a subclass of NSViewController,
and instead of using a modal window I'd use a sheet, which your table
view controller would be the delegate of. All your logic gets to stay
in one place
On 07/02/2010, at 3:52 PM, Trygve Inda wrote:
> The checkboxes window is in is own nib
[]
> Any drawback to this?
>
> It seems like overkill to create a custom class to manage the checkbox
> window when all the checkboxes are controlled by bindings and there is only
> an OK/Cancel button.
>
>
I have a rather complex NSTableView that is managed by a custom class
"TableController". This manages the array of data that the table will
display
I need to be able to put up a very simple modal window with checkboxes for
each possible column (to set show/hide state) and OK/Cancel buttons.
The c
10 matches
Mail list logo
