+
+
+
+ Syntax: What it all means
+
+
+ Commands in this documentation are presented as follows:
+
+
+
+
+ Some defines are true/false values. These are considered true if the value is defined, and false otherwise.
+
+
+
+
+ NSIS Syntax Highlighting
+
+ The ExperienceUI SDK Documentation also uses syntax highlighting for various NSIS commands and parameters. Here's how it works:
+
+
+ NSISCommand /NSIS /Parameter NSIS_String_Not_Quoted "NSIS String in quotes $WITH_VAR"
+ !directive XPUI_DEFINE_SYMBOL "XPUI Define Value"
+
+
+
+
+
+
+ Inserting Commands
+
+
+
+
+
+ In the ExperienceUI, all has a set order and organization. The method for inserting commands and setting settings has been fine-tuned for the best
+ possible performance and the easiest possible setting of settings.
+
+ To insert ExperienceUI-related macros, you must include the XPUI.nsh file before the point in the script where the macro is inserted. If you fail to do
+ this, the NSIS compiler will halt.
+
+ If you want custom GUI settings, you must define them before inserting the first language into your script.
+
+ To change strings for any given language, you will need to define the string in the language you want it in, and then insert the associated
+ XPUI_LANGUAGE macro.
+
+ To change the UI that is used, you must define XPUI_UI, XPUI_UI_IDDINST, XPUI_UI_BOTTOMIMAGE, or XPUI_WANSIS_UI before including XPUI.nsh. This is because some of the branding image controls are referenced in every page, and MakeNSIS requires that these controls be present in the current UI file.
+
+
+
+
+ |
+
+
+
+