On Wed, Jun 4, 2008 at 8:46 PM, Trygve Inda <[EMAIL PROTECTED]> wrote:
> Thoughts?
It sounds like you're going for the "two instances of the same class" approach.
In which case, you have a single combined controller class with your
singe set of outlets and actions. Set your File's Owner in each
> On Wed, Jun 4, 2008 at 8:17 PM, Trygve Inda <[EMAIL PROTECTED]> wrote:
>
>> I'd need two instances of WindowController.
>
> The way I see it, you have a choice: either a single instance of a
> controller with 2n outlets, or two instances of a controller with n
> outlets.
>
> If you want to hav
On Wed, Jun 4, 2008 at 8:17 PM, Trygve Inda <[EMAIL PROTECTED]> wrote:
> I'd need two instances of WindowController.
The way I see it, you have a choice: either a single instance of a
controller with 2n outlets, or two instances of a controller with n
outlets.
If you want to have "one controller
> On Tue, Jun 3, 2008 at 10:21 PM, Trygve Inda <[EMAIL PROTECTED]> wrote:
>
>> Since the IBOutlets in Main point to a different Nib than the IBOutlets in
>> Aux (even though they are functionally identical) is there a good, clean way
>> to manage this?
>
> Can you not wire the IBOutlets in Aux to
On Tue, Jun 3, 2008 at 10:21 PM, Trygve Inda <[EMAIL PROTECTED]> wrote:
> Since the IBOutlets in Main point to a different Nib than the IBOutlets in
> Aux (even though they are functionally identical) is there a good, clean way
> to manage this?
Can you not wire the IBOutlets in Aux to the File's
> On Jun 3, 2008, at 2:48 PM, Trygve Inda wrote:
>
>>> Hi, Trygve,
>>>
>>> With regard to your code duplication, I would use a common
>>> NSWindowController superclass, with a subclass for your main window
>>> and a subclass for your aux window. Then you can just use the right
>>> nib name in ea
On Jun 3, 2008, at 2:48 PM, Trygve Inda wrote:
Hi, Trygve,
With regard to your code duplication, I would use a common
NSWindowController superclass, with a subclass for your main window
and a subclass for your aux window. Then you can just use the right
nib name in each of them, but leave the
> Hi, Trygve,
>
> With regard to your code duplication, I would use a common
> NSWindowController superclass, with a subclass for your main window
> and a subclass for your aux window. Then you can just use the right
> nib name in each of them, but leave the rest of the code identical.
>
> Cheer
Hi, Trygve,
With regard to your code duplication, I would use a common
NSWindowController superclass, with a subclass for your main window
and a subclass for your aux window. Then you can just use the right
nib name in each of them, but leave the rest of the code identical.
Cheers,
Hi All,
Sorry for the vague subject title... Let me explain.
I have one window per attached screen so at least one, but perhaps 3 (for
example). There is always one "main" window and the others are considered
"aux windows".
The Main window has 4 groups of controls (A, B, C, D).
The Aux windows h
10 matches
Mail list logo
