Board index » cppbuilder » More details from Tom

2007-04-16 06:22:48 PM
cppbuilder79
First, thank you for trying to help me. I will try to explane.
I have a Borland C++ 4, application which I try to convert into C++ BDS
2006.
This is an MDI-application and I have three different child-windows. Each of
these child-windows run their own use-case
If you understand what I mean, and the user can select to start one or all
of them at the time. They can all run simoustainly. Inside the child-windows
I display a dialog box
Which is sutable to handle the actual use-case. I dont remember but I think
I once saw this example on the internett. It was at least 10 years back.
I would like to(I think I have to) use a simular techniqe on my new(updatet
application). Here is part of my old code.
TMDIClient* mdiClient =
TYPESAFE_DOWNCAST(GetMainWindow()->GetClientWindow(), TMDIClient);
if (mdiClient)
{
// Here I create my dialog
TransSosiFilDlg* DlgSosiFil = new
TransSosiFilDlg(GetMainWindow()->GetClientWindow());
// Here I create a new child window. Se the parameters. DLG_TRANSFILSOSI is
the dialogs unique number in the .res-file
TWsktransMDIChild* DlgChild = new TWsktransMDIChild(*mdiClient,
DLG_TRANSFILSOSI, "Chils windows Caption", (TWindow*)DlgSosiFil);
DlgChild->Create();
}
I really hope I can do this with C++ BDS 2006. If you need more info please
let me know.
tom
 

Hi,
you need to decide if you want to convert the framework,
i.e. do you want to now use VCL instead of OWL in that
application? Maybe you should create a new VCL application
and see if RAD lets you quickly get an interface similar
to your older app, which would mean that adding the core
functionaliy to a new VCL app might be one approach to doing
the conversion.
--Craig
 

On 16 Apr, 20:14, Craig Farrell < XXXX@XXXXX.COM >
wrote:
I do not want to convert the framework. I have started to create a new
VCL-application,
however some of my old classes and buiseness logic where OWL is
involved must be rewritten (converted).
Working with the C++ Builder in BDS 2006 is plesant but I would like
to use the way that I handle dialogs in
child-windows.
I have got some answers from Hans and I think I will try what he says.
Dialog->Parent = this, or Dialog->Parent = MDIChild.
tom
 

{smallsort}