Re: Initialize Second Dialog

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Of course one can always get around such considerations by rejecting the
concept "CDialog is a dialogue" and substituting "CDialog is a wrapper
around a dialogue into which a dialogue may, or may not, have been
inserted".

I see what you mean.

I must look at .net one of these days. But I use a lot of multiple
inheritance and bit fields and I suspect that converting a large C++
application to that framework would be tedious.

Although MI is not supported, you can have a class which supports
multiple interfaces. However I am not really sure what advantage, if
any, you would gain by porting your code over to .Net. Best you can do
is to use CLI and keep on using existing code in .Net.

--
Ajay

.

Relevant Pages

  • Re: Initialize Second Dialog
    ... concept "CDialog is a dialogue" and substituting "CDialog is a wrapper ... Certainly bad design, as you put it (from the aesthetic ... point of view), but also, I would argue, bad object-orientation leaving half ...
    (microsoft.public.vc.mfc)
  • Re: MESSAGEBOX?
    ... we had no choice as we had no wrapper. ... >> were converting to multi-lingual, and we wanted the string translation to ... >> happen inside of the messagebox function. ... > it become a CHRin the dialogue. ...
    (microsoft.public.fox.programmer.exchange)