You can find dialogs of components settings on three levels:
- Platform level available by “Tools” menu -> “Platforms” -> selected platform, e.g. VCL or .NET -> “Components” tab. You can add here new components mapping or change existing components settings. It will be applied to all new Sisulizer projects created for selected platform.
- Project level available by “Project” menu -> “Components” -> submenu with sources list. if you select item from this list, Sisulizer opens components dialog for selected source. All changes, or added new components are applied only to currently selected source in Project Tree of edited project, without influence on your other projects for this same platform. However, you have the possibility to release new mapped components for other projects via “Publish” button in dialog toolbar “Components”. This feature copies new mapped components to components list on platform level. You can’t publish components already existing on platform level, butÂ changed on project level. This solution prevents accidental overriding for already existing components mapping on higher level with specific values from lower level. If you would like to change components settings for all your projects you need to do it on platform level. This same dialog is available also via context menu of source item in project tree.
- All changed components are indicated by “Overloaded” captionÂ in “status” column, but you can always restore default components settings by click on “restore” button available on “components” dialog toolbar.
- You can export your components list to external file, and next use it on with Sisulizer installation on other computer. If you export components list from project level, you can import it to other project without adding (publishing) this list to main (platform) components list. You can import components list with “higher” level to “lower” level, but not vice versa.