🚀 go-pugleaf

In article <ejalbert-AE5652.14240329102000@nntp.stanford.edu>, Eric
Albert <ejalbert@stanford.edu> wrote:

> In article <291020001117102847%mjg@mac.com>, Joey Gray <mjg@mac.com> 
> wrote:
> 
> > it's been a while since i've done this, but wouldn't your code look
> > something like this:
> > 
> > {
> >   StDialogHandler outerHandler( whatever... );
> > 
> >   do {
> >     message = outerHandler.DoDialog();
> >     if (message == msg_OpenOtherDialog) {
> >       StDialogHandler innerHandler( whatever... );
> > 
> >       // deal with the inner dialog here...
> >       message = msg_OK; // or msg_Cancel...whatever...
> >     }
> >   } while (message != msg_OK && message != msg_Cancel);
> > }
> > 
> > you could deal with the inner dialog in an entirely different method
> > (which is what i would do) but still set the "message" variable for the
> > outer dialog, after having dealt with the inner dialog, such that you
> > exit your while loop cleanly.
> 
> That's not all that ideal, because it requires the class that includes 
> the StDialogHandler for the first dialog to know about the second, and 
> I'd rather not do that -- it makes that part of the code a good bit 
> harder to maintain.  It would work, but I'm hoping there's a better 
> solution.

okay, so your objection is that the first dialog handler must know
about the second dialog. doesn't it have to? how else do you open the
second dialog from within the first dialog?

obviously there's more to the code than in the example that i
presented, but the general idea is there. in the outer dialog, when you
click on the button which is supposed to trigger the open of the inner
dialog you call the method(s) which deal with the inner dialog. don't
you have to do at least something like that in your current code?

perhaps something like this:

void COuterDialog::DoDialog( ... )
{
  StDialogHandler outerHandler( ... );

  do {
    message = outerHandler.DoDialog();
    if (message == msg_OpenOtherDialog) {
      CInnerDialog::DoDialog( ... );
      message = msg_OK; // or msg_Cancel
    }
  } while (message != msg_OK && message != msg_Cancel);
}

void CInnerDialog::DoDialog( ... )
{
  StDialogHandler innerHandler( ... );

  do {
    message = innerHandler.DoDialog();
    // ...
  } while (message != msg_OK && message != msg_Cancel);
}

perhaps you can have the inner dialog handler return some kind of
indicator as to how to deal with the outer dialog.

how does the code you have now pass control from the outer dialog to
the inner dialog?

-joey