<font color="#ff0000">VB to VC GUI conversion tool?</font>
-
I've taken the (enlightened?) route of developing an application GUI in VB, getting the customer to accept the GUI, then developing the whole app. (including GUI) in VC. I've now reached the point where the customer is happy with the GUI and I have to start again in VC. Does anyone know of any tools that will translate VBs .frm files into a VC resource file and save me a heap of time? Derek.
-
I've taken the (enlightened?) route of developing an application GUI in VB, getting the customer to accept the GUI, then developing the whole app. (including GUI) in VC. I've now reached the point where the customer is happy with the GUI and I have to start again in VC. Does anyone know of any tools that will translate VBs .frm files into a VC resource file and save me a heap of time? Derek.
The import button from the Resource Editor's insert new resource dialog gives the option of importing a vb .frm file. I haven't used it so I don't know how reliable it is. Michael :-)
-
The import button from the Resource Editor's insert new resource dialog gives the option of importing a vb .frm file. I haven't used it so I don't know how reliable it is. Michael :-)
Thanks for the tip. I'd never noticed before :-O
-
The import button from the Resource Editor's insert new resource dialog gives the option of importing a vb .frm file. I haven't used it so I don't know how reliable it is. Michael :-)
Never noticed that before. It seems to work okay with simple forms, but put anything in other that the plain controls, e.g. activeX controls such as the progress bar, and it gets upset. Does anyone know how to get it to detect these correctly. It gives you the option of editing the file. Giles
-
Never noticed that before. It seems to work okay with simple forms, but put anything in other that the plain controls, e.g. activeX controls such as the progress bar, and it gets upset. Does anyone know how to get it to detect these correctly. It gives you the option of editing the file. Giles
Even more annoyingly, it ignores combo boxes.
-
I've taken the (enlightened?) route of developing an application GUI in VB, getting the customer to accept the GUI, then developing the whole app. (including GUI) in VC. I've now reached the point where the customer is happy with the GUI and I have to start again in VC. Does anyone know of any tools that will translate VBs .frm files into a VC resource file and save me a heap of time? Derek.
There's no need for a conversion tool. Just import the *.frm files to your resource script. Be sure to insert all ActiveX/OCX to your project first. Than right click the resource script, select import and file type *.frm. Thats all. Hope this helps.. Jens
-
I've taken the (enlightened?) route of developing an application GUI in VB, getting the customer to accept the GUI, then developing the whole app. (including GUI) in VC. I've now reached the point where the customer is happy with the GUI and I have to start again in VC. Does anyone know of any tools that will translate VBs .frm files into a VC resource file and save me a heap of time? Derek.
I've had a quick look in the MSDN. It would appear that there are quite a few limitations! Apparently (quote from MSDN): The following controls are implemented in a reduced-functionality way or ignored, due to differences between the Visual Basic run-time and the Windows dialog functionality: +Drive and directory list boxes. These are converted to a Windows list box, which can be filled. +MDI forms. Imported as a normal dialog box. Menus are ignored. +Data controls. +Line and shape controls. +Horizontal and vertical scroll bars. +Timers. +Printers. +Screens. +Clipboards. +Queries. +Apps. There are also limitations with respect to properties and nested controls: Several properties of Visual Basic controls are implemented only by Visual Basic and have no equivalent in Windows dialog boxes and controls. Examples include setting font and color properties for individual controls. Nested controls, possible in Visual Basic, do not translate into the Visual C++ environment. In the Visual Basic environment, controls can be nested inside of each other. You can set the Visible state of all of the nested controls by setting the outermost control to Visible. In the Visual C++ environment, the visibility of the controls is a run-time feature. One solution is to move the overlapping controls into separate dialog boxes. Then have the code create the dialog boxes as needed, with the main dialog box as a parent window. Oh well, at least it will layout some of what I want :confused: Derek.