Skins are visual attribute definitions for application controls that are stored in the skin file, [set the File Name variable].skin. Control skins define only the visual attributes that are a part of a theme for an application.
In CA Gen ASP.NET applications, you can define control skins for each control type in a separate file, or you can define all the control skins for a theme in a single file. The <themename> directory for a theme must include all the control skins that are a part of the theme.
The control skin overrides the appearance settings for the control in the Navigation diagram. However, the appearance settings of a control through dynamic attributes or Dot Notation override the settings in the control skin.
CA Gen supports default control skins. A default control skin automatically applies to the all the controls of the same type when a theme is applied to the ASP.NET application. A default skin has the following format:
<ServerControlType runat=”server” property1=”value1” property2=”value2” ……/>
For example, this is the default control skin entry for a single line entry field:
<Gen:ASPXSingleLineEdit runat="server" Height="20px" Width="100px" ForeColor="Red" BackColor="#FFE4C4" Font-Name="Script" Font-Size="14pt" Font-Bold="false" Font-Italic=”true” Font-Strikeout=”false” Font-Underline=”true” BorderStyle="groove" BorderColor="#FF0000" BorderWidth="1pt"/>
This default skin applies to all SingleLineEdit controls on pages that use the theme.
CA Gen provides a sample skin, Gen_Sample.skin, in the CA Gen samples\ASP.NET directory.
Note: CA Gen does not support named skins that apply to a specific instance of a control type.
|
Copyright © 2013 CA.
All rights reserved.
|
|