OverviewAppearanceVersionAdvancedCode SigningSkin
AutoPlay will automatically choose between conserving memory and maximizing speed in order to achieve optimal performance. This is the recommended setting.
Each page's data will be cached in memory after its initial display. If any of these pages are viewed again, loading time is reduced, however memory usage will increase on the end user's system throughout the application.
Do not cache page data in memory. Each page's data will be reloaded from disk or drive, minimizing memory usage on the end user's system.
Enables a right to left reading order throughout your project. When checked, all Button, Label, and Paragraph objects throughout your project will have a right to left reading order. As well, all Input, ComboBox, Tree, and List Box objects added after this option is enabled will have their reading order set to right to left by default.
Note: Any Input, ComboBox, Tree, List Box, and RichText objects present in your project before this option is enabled will keep their individual read order settings.
Tip: You can change the read order for Input, ComboBox, Tree, List Box, and RichText objects through their individual Object Properties.
This section specifies which requested execution level to include in the AutoPlay application's manifest for running on Windows Vista or later. AutoPlay applications are generally built using the default "As invoker" setting, however may need to be changed given the requirements of your project. For more information to help make this decision, and other required changes and feature limitations, see Running on Windows Vista or Later.
Note: If the user disabled UAC on their system (changed from default), or has configured it differently, these settings will have no effect. If your application requires additional privileges, you must include your own administrator detection and handle how you wish to proceed if the requirement is not met. See the System.GetUserInfo action to perform administrator detection.
Note: Changing the application manifest to "Highest available" or "Require administrator" is only supported on Windows 2000 or later in AutoPlay Media Studio's design environment, and only available in the Commercial version.
Note: For more information on the settings below and general Windows Vista or later information, see the Running on Windows Vista or Later topic.
The AutoPlay application runs with the same access token as the parent process. For example, if the user is logged in as a standard user, those are the privileges they will inherit during the running of the application. This option is generally used for AutoPlay applications that are presentations or menus, where you are certain you do not need access to protected areas of the operating system (file system/registry). This includes access directly by the AutoPlay application, and the launching of external programs that require these permissions (unless they are designed to handle their own permission detection and notification). See Running on Windows Vista or Later for additional details.
The AutoPlay application runs with the highest privileges the current user can obtain. This setting is designed for applications that can be run by all users. It is most useful for applications that require privileges above that of a limited user, but less than a full administrator.
The AutoPlay application requires to be run with the full access token of an Administrator. This setting should be used if your AutoPlay application needs to make changes to protected system locations (file system/registry) that are typically writable to only by Administrator users. This includes access directly by the AutoPlay application, and the launching of external programs that require this access (unless they are designed to handle their own permission detection and notification.)
Note: If the user disabled UAC on their system (changed from default), this setting will have no effect. In addition to this setting, you must include your own administrator detection and how you wish to proceed if the requirement is not met. See the System.GetUserInfo action to perform Administrator detection.