How skins work
+ ++ In the ExperienceUI world, there are two ways of doing the actual skinning. The first - and most common - is the conventional + NSIS-based method of skinning. The second is skinning using an external plugin, such as WAnsis. The + define XPUI_SKIN applies only to conventional skins; XPUI_WANSIS_SKIN applies to installers using WAnsis. +
++ Blah +
+ +Basic Settings
+ + + + + + + + +Abort Warning
++ + + An abort warning is a message that shows when you click Cancel. If you don't use an abort warning, the installer will close + as soon as you click Cancel. + + + + +
+
+ If you have an Abort Page in your installer, you may want to use an automatic abort warning in order to make the Abort page + trigger properly. If you aren't using the ExperienceUI's built-in abort warning system, you can insert the following + function to properly invoke the Abort page.
+
+ +
Expand Abort function+ + +
+
+
+ I just realized that though this "mystery" variable has been used with the ExperienceUI forever past, it never got a + mention in the documentation. Here's why it's here:
+
+ Note: In ExperienceUI versions <=1.1, the variable was $NOABORTWARNING. It was renamed to $NOABORTWARNING in versions 1.11.
+
+ The Abort and InstSuccess pages, as you may have noticed, take advantage of an NSIS hack to make the Cancel button close + the installer window without a prompt. The $XPUI_NOABORTWARNING variable is always declared, even if it isn't used, because + of the way the ExperienceUI references variables. When the Abort page or the InstSuccess page is triggered, it uses +
StrCpy $NOABORTWARNING 1 to make the .onUserAbort function quit the installer immediately after the Cancel
+ button (which has become the close button) is clicked.+
+ The thing is, when I created the first tests of the ExperienceUI code, I was also working on a few installers for some + people. The installers used the Modern UI, but with many custom pages (such as the Install Success page) that later + found their way into the ExperienceUI. I used the $NOABORTWARNING variable to keep track of whether the Cancel button + cancelled the installer or closed the installer window. The variable was renamed to $XPUI_NOABORTWARNING in ExperienceUI version 1.11.
+
+ You can use this variable too - all the ExperienceUI pages and functions understand it. If you know basic window + manipulation (very C++), you can do this quite easily: Disable the "Next" button, and set $XPUI_NOABORTWARNING to 1. When you + click Cancel on the affected page, the installer will quit instantly. Optionally, you can set the text on the Cancel + button to Close or whatever. +
Dialog Colors
++ + + +
+ + + +Navigation Buttons
+ + + ++ After defining custom text for buttons, that text will be used in the next language inserted. Defining any custom button + text after inserting the last language will have no effect in the final installer. +
+ + + +Page Background Image
+ ++ You can show a bitmap in the background of your installer's pages. Support for thie feature is still experimental, but it should work + for most pages. Note that Stardock WindowBlinds 5.0 can cause problems with this, and 4.x versions are known to cause radio buttons and + check boxes to not work at all. Also, avoid using icon controls that show an icon with a 32x32 image that contains an alpha channel, as this causes the background + of the icon controls to show up as black. +
+ + + +
+ A note on skins:
+
+ When you use a page background image, you may need to change the Left Logo image. If you want to allow the user of your skin to turn the
+ page background image on or off, you may want to use the following code to be sure that the Left Logo is changed properly.
+
+ Expand code
+