Soluling home Document home
Use this sheet to specify Delphi related options.
Specifies various options.
|Inherited forms in a hierarchy||If checked, inherited forms are shown hierarchically on the project tree.|
|Load inherited forms into the grid||If checked, the grid loads the strings of the selected form and all strings of the inherited forms as well.|
|Scan All Images||If checked, all images (including form and resource images) are scanned.|
|Scan visual properties of forms||If checked, all visual properties such as Width and Height are scanned. Uncheck this if you want to make your project file smaller.|
|Use visual editors||If checked, a visual form editor is shown when a form node is selected in the project tree.|
|Use auto-mapping||If checked, a visual form editor uses automatic mapping for 3rd party controls.|
Specifies the context method of string resources. Possible values are:
|Use DRC file||Soluling uses the DRC file to get unique and immutable resource strings context values. This option is effective only if a DRC file has been specified. If not, resource ids are used.|
|String value||Soluling uses string values as context values. This is safe, even if you modify and recompile your application. However, if the application has the same text in two or more resource strings, this method brings only one row to the project file. So all instances of the same text will share the same row, and you can no longer translate them differently.|
|Resource id||Soluling uses resource ids as context values. This is potentially dangerous because the Delphi compiler may change the resource strings ids next time you compile your project. Even Soluling makes everything to resynch changed ids correctly; this may cause to loss of existing translations, or even mixing two existing translations. Both errors are very hard to locate and fix.|
Specifies the DRC file. This is enabled if Context method of string resources is Use DRC file.