How to verify a ModelMaker Code Explorer installation?

This document explains how to verify your ModelMaker Code Explorer installation and how to solve installation problems.
Applicable to versions MMX 1.x - 12.x The text assumes a MMX 12.x installation, for older versions, substitute "12" with "1" - "11" where applicable.

Directories and files

You should have these directories (actual path names depending on your actual install dir / drive)

  • C:\program files\ModelMakerTools
    The root directory, does not contain files
  • C:\program files\ModelMakerTools\Midex\12.00
    Or whatever version or you installed. Contains all explorer related files such as mmx_bds17.dll.dll, the user manual etc.
  • C:\Documents and Settings\[USER NAME]\Application Data\ModelMakerTools\Shared
    The user data directory containing files shared with other ModelMaker Tools products. No files required in this directory, but it can contain auto-created files like SharedSettings.ini.
  • C:\Documents and Settings\[USER NAME]\Application Data\ModelMakerTools\Shared\Templates
    This directory should contain the predefined templates and other templates you added. For example ArrayProp_List.pas.

If any of these directories or files is missing you need to run the installer again.

Registry settings: HKEY_LOCAL_MACHINE

You should have these keys:

  • HKLM\Software\ModelMaker\midex\12.0
    containing at least a string value named InstallDir pointing to the actual install path. For example: "C:\program files\ModelMakerTools\Midex\12.00" (omit quotes).
  • HKLM\Software\ModelMaker\Shared
    containing at least has a string value named RootDir pointing to the Shared directory - a user app data sub driectory. For example: "C:\Documents and Settings\[USER NAME]\Application Data\ModelMakerTools\Shared" (omit quotes).
  • HKLM\Software\ModelMaker\Shared\Templates
    containing at least has a string value named RootDir pointing to the Templates directory. For example: "C:\Documents and Settings\[USER NAME]\Application Data\ModelMakerTools\Shared\Templates" (omit quotes).

If any of these keys / values is missing, you may either run the installer again or manually add them. Make sure you enter the correct directory names.

Registry settings: HKEY_CURRENT_USER

You should have these keys:

  • HKCU\Software\ModelMaker\Shared
    containing at least has a string value named RootDir pointing to the Shared directory - a user app data sub driectory. For example: "C:\Documents and Settings\[USER NAME]\Application Data\ModelMakerTools\Shared" (omit quotes). This is the same value as stored in HKLM
  • HKCU\Software\ModelMaker\Shared\Templates
    containing values that are the registered templates. For example:
    value name=Array Property
    value string data="C:\Documents and Settings\[USER NAME]\Application Data\ModelMakerTools\Shared\Templates\ArrayProp_List.pas",Wizards

This key and it's values are non-essential for ModelMaker Code Explorer. Registering a new code template will auto create whatever is missing.

You do not need any keys or values in HKCU\Software\ModelMaker\Midex\12.0 or any of its sub keys

Delphi IDE Integration

The ModelMaker Code Explorer installer integrates the explorer with all installed Delphi IDEs. To change integration at a later time, use the explorer | Properties | IDE Integration tab. Changing IDE integration settings requires restarting Delphi.

Technically Delphi IDE integration is for each Delphi IDE done through a string value in HKEY_CURRENT_USER.

HKCU\Software\Borland\Delphi\5.0\Experts - for Delphi 5
HKCU\Software\Borland\Delphi\6.0\Experts - for Delphi 6
HKCU\Software\Borland\Delphi\7.0\Experts - for Delphi 7
HKCU\Software\Borland\BDS\5.0\Experts - for Delphi 2007
HKCU\Software\CodeGear\BDS\6.0\Experts - for Delphi 2009
HKCU\Software\CodeGear\BDS\7.0\Experts - for Delphi 2010
HKCU\Software\Embarcadero\BDS\8.0\Experts - for Delphi XE
HKCU\Software\Embarcadero\BDS\9.0\Experts - for Delphi XE2
HKCU\Software\Embarcadero\BDS\10.0\Experts - for Delphi XE3
HKCU\Software\Embarcadero\BDS\11.0\Experts - for Delphi XE4
HKCU\Software\Embarcadero\BDS\12.0\Experts - for Delphi XE5
HKCU\Software\Embarcadero\BDS\14.0\Experts - for Delphi XE6
HKCU\Software\Embarcadero\BDS\15.0\Experts - for Delphi XE7
HKCU\Software\Embarcadero\BDS\16.0\Experts - for Delphi XE8
HKCU\Software\Embarcadero\BDS\17.0\Experts - for Delphi 10 Seattle
HKCU\Software\Embarcadero\BDS\18.0\Experts - for Delphi 10.1 Berlin
HKCU\Software\Embarcadero\BDS\19.0\Experts - for Delphi 10.2 Tokyo

For each Delphi version installed you should find a string value named MidexExpert " Correct spelling is essential to avoid problems with future installs! The string data should point to the actual explorer dll as found in the MMX install directory. For example (Delphi 2010)
value name =MidexExpert
value string data =C:\program files\ModelMakerTools\Midex\11.00\mmx_bds7.dll

The dll names for the Delphi IDEs are: midexd5.dll - midexd7.dll (Delphi 5 - 7) and mmx_bds5.dll - mmx_bds19.dll (Delphi 2007 - Delphi 10.2 Tokyo)

If ModelMaker Code Explorer is not loaded by Delphi this is revealed by not having the MMX menu item in the IDE View menu. This is caused by a missing MidexExpert value for that IDE. You can manually add the value. Make sure you define the correct dll for that IDE.