|
|
ezScript tasks |
SolutionClearing ezParse Rules through ezScript ( /C )The following syntax is used to clean existing parse rules /C EZPFileName [/LOAD] [/CLEAN] [/open] /CLEAN: removes any existing Text and XML rules, leaving an empty rule called 'Standard' for each file extension present. For example: Catalyst /C "C:\Catalyst files\my_cat8_ezparse.ezp" /LOAD /CLEAN /open Changing the font used in your dialogs ( /F )Using the /F switch, you can change the dialog fonts of an executable in your TTK. /F TTKFname AppFname [FontName:FontName] FontSize [/open] When changing the dialogs font it is required that the executable containing the dialog you wish to change the font for is in the same folder as the TTK when the command is executed. Also when the command is executed the full path must be given to the file. Below you can see an example of the change dialog font command being executed through the command line. Catalyst /F "C:\Catalyst files\testTTKs\test.ttk" "C:\Catalyst filessource\blog.dll" FontName:"MS Sans Serif" 26 /open
Applying settings through ezScriptThe best way to keep consistency in a project is by using User Profiles. They are used to store and retrieve configuration options. These options are set using the Alchemy Experts or General Options dialog box. You can save User Profiles containing your configuration options and later use these options by loading these Profiles. How User Profiles work is as follows:
Catalyst /C c:\French\BuildOpts.ini /LOAD You can find the complete reference to these ezScript commandsin Alchemy Catalyst: Help menu > ezScript reference.
NotesText Related topics
Products or Versions Affected
Last updated with Catalyst 9.0
|