VCL Form Editor

This editor gives a detailed view of a Delphi/C++Builder application's form resource. It includes both a visual (wysiwyg) view and a form data view. The editor contains versatile configuration options to get the best possible view of the form. To achieve best possible results Multilizer partners with well-known component library vendors, and naturally with CodeGear.



Visual (wysiwyg) view

Visual View contains the form visualized and a object tree and object inspector -- just like Delphi or C++Builder tools.

  • By default the visual editor strives to give a perfect view of the form. To achieve this, Multilizer co-operates with established Delphi/C++Builder component library vendors.
  • Components that Multilizer doesn't know are mapped to "TMLZ2007Components", which give an estimate of how the component might look like. This mapping is using Multilizer mapping table. Read more about mapping in Visual Editor Options
  • Users of Multilizer can use their mapping customizations in latest version of Multilizer.

Screenshot of Multilizer 2009 VCL Form Editor: object treeview, object inspector and form preview.

Click to enlarge.

Form data view

This view shows the formdata as it is in Delphi/C++Builder.

Configuration - Visual Editor options

Editor Options tab

The options are used for configuring standard options in the editor.

Use component mapping. If this is not checked and there are classes that Multilizer doesn't know, the components are not shown at all.

Mapping files tab

On this tab user can specify the mapping files used for component mapping.

By default there is one (system) mapping file defined; it's the same mapping file that is used in Multilizer. It contains ~1000 components that are mapped to a component that Multilizer can show.

There can be multiple mapping files in the list. Mappings are prioritized; first file's mapping info is used first, then second if necessary, etc.

Mapping options tab

Use Multilizer mode for mapping controls. When checked, Multilizer first tries mapping through the mapping files then using editor's own classes. The result is closest to what users achieved in Multilizer.

Show mapping log. When checked, user will see how classes are being mapped to Multilizer's internal classes.

Show mapped components with color codes. When checked, mapped components have Magenta caption.

Use fallback class. When checked, components that can't be mapped and are not recognized will be shown as a yellow placeholder.

To achieve best results, use the following options:

[ ] Use Multilizer mode for mapping controls (Mapping options tab).
[X] Use component mapping (Editor Options tab).
If the editor returns any error, try first unchecking "Use component mapping".

To mimic Multilizer, user the following options:

[X] Use Multilizer mode for mapping controls (Mapping options tab).
[X] Use component mapping (Editor Options tab).


Multilizer Visual Editor doesn't always show the components properly. See previous chapter on the settings to configure this.

If there are components that Multilizer doesn't visualize correctly or it doesn't show them at all, contact us; send the component mapping log to us so that we can see how components have been mapped. If there are any 3rd-party controls that Multilizer doesn't know, we'll more than likely contact the component vendor.


Multilizer's goal is to give users as good experience as possible in visualization of forms in their Delphi/C++Builder localization projects.

To achieve this goal, Multilizer partners with established component library vendors:

The following two pictures clearly show how partnership has affected the quality of Multilizer's Visual Editor.

This picture illustrates how a form using heavily 3rd-party components looks like when using component mapping.
Raize component demo as displayed in Multilizer 6.2 mode in Multilizer 2009.
(Click to enlarge)

This picture illustrates the same form after starting co-operation with the 3rd-party vendor.
Raize component demo as displayed in Multilizer 2009.
(Click to enlarge)