Resolve conflicts when importing duplicate client controls

You can import a different version of a client control and overwrite the existing control. The .dll hosting the existing control will be replaced by the importing library. Conflicting client controls will be detected upon import of the new client control .dll.

Note: Conflict detection is based solely on the name of the control. Library filenames or versions have no affect on conflict detection.

For example, if you import a client control .dll containing the two controls MathControl and TrendControl and the current library contains controls of the same name, the Import Client Control dialog box will display:

The existing client control .dll will be replaced, and the new control will now be available in the library.

If you see "Remove" in the Proceeding will column, it means there are controls in the current library that are not in the importing library. Because the hosting .dll must be replaced to resolve the conflicting controls, any controls that are in the current.dll but not in the importing .dll will be removed upon proceeing with the import.

For example, importing a client control .dll containing the controls MathControl and DatabaseControl and the current library contains MathControl and TrendControl, TrendControl will be removed from the library upon import.

The Import Client Control dialog box will prompt you to acknowledge the removal:

The library will be replaced and TrendControl will be removed upon completion of the import.

Restart WindowMaker to update the controls in the Graphic Toolbox.

Note: If you have imported a newer version of client control already embedded in a symbol, restarting WindowMaker and refreshing the graphic thumbnail will not update the contents of the control. You must edit and save the symbol for the new client control to be reflected in the thumbnail.