These properties control specific types of controls created by Iron Speed Designer.
These properties control specific types of controls created by Iron Speed Designer.
Property |
Description |
||||||||||||
Consumers |
Designates a “consumer” of the button event. When the button is activated, the application creates an “event” that informs other controls that the button has been clicked. This allows other controls to take action based on the event. This property designates which component, if any, receives the event.
|
||||||||||||
ControlToUpdate |
Specifies the name of the dropdown list control updated by this button.
|
||||||||||||
FieldValue |
Specifies the name of the database field that populates the dropdown list updated by the Quick Add button.
|
||||||||||||
RedirectArgument |
URL arguments, if any, to pass to the page being displayed. There are several special arguments described in Button Actions - Substitution Variables. |
||||||||||||
RedirectURL |
The URL of the page to be displayed when the button is clicked. There are several special arguments:
|
||||||||||||
RowDisplayAction |
Specifies the row display behavior when the ‘Expand’ button is pressed.
|
||||||||||||
SendEmail<Number>From |
Specifies the email address to use in the From field of an email. The email address can be specified as a constant or as a substitution variable. If it is a substitution variable, then the email address is taken from a field in the Table or Record control during application run-time. Multiple email addresses should be separated by comas (,). Email address should take one of these formats: · A constant · A substitution variable · Display name constant <Email address constant> · Display name constant <Email address substitution variable> · Display name substitution variable <Email address constant> · Display name substitution variable <Email address substitution variable> Substitution variables have the format: {ControlName:NoUrlEncode:FV:FieldName} See Button Actions - Substitution Variables for details on substitution variables. Property numbering starts with 1, must be an integer, and should be sequential. For example, adding three send email actions using the Button Action Wizard creates this sequence of SendEmail<Number>From properties: SendEmail1From SendEmail2From SendEmail3From If you are adding custom properties through the Property Sheet, make sure the properties are numbered sequentially. If numbering is not sequential, then send email code will be created only for those send email actions that are numbered sequentially. For example, if you have added three send email actions and used numbers 1, 3, 4, send email code will be created only for the first send email action.
The text of all send email related properties is stored as encoded (using URL encoding). This allows you to use different special characters (for example XML code). We strongly recommend using the Button Action Wizard to add send email-related properties. This helps avoid unnecessary problems and assures correct operation of your application. |
||||||||||||
SendEmail<Number>To SendEmail<Number>CC SendEmail<Number>BCC |
Specifies the email address to use in the To, CC, and BCC fields of an email. See SendEmail<Number>From for numbering details. |
||||||||||||
SendEmail<Number>Subject |
Specifies the subject of the email. See SendEmail<Number>From for numbering details. |
||||||||||||
SendEmail<Number>ContentURL |
Specifies the URL of the web page used as content of the email. See SendEmail<Number>From for numbering details. |
||||||||||||
SendEmail<Number>Content |
Specifies the text used as content of the email. See SendEmail<Number>From for numbering details. |
||||||||||||
SendEmail<Number>EmbedImages |
Supplements the SendEmail<Number>ContentURL property.
See SendEmail<Number>From for numbering details. |
||||||||||||
SendEmail<Number>ForRecord |
This property is used to create send email actions.
See SendEmail<Number>From for numbering details. |
Property |
Description |
OnMouseOut OnMouseOutDesc |
JavaScript executed when your mouse leaves the button. |
OnMouseOver OnMouseOverDesc |
JavaScript executed when your mouse is over the button. |
The ASP.NET controls have a wide variety of properties that can be used to govern the controls’ behaviors.
Property |
Description |
ImageUrl |
The URL of the button image to be displayed.
Example: Binding an Image tag in ...\MyApp\Shared\test.aspx to "image1.gif" will create a reference to ...\MyApp\Shared\image1.gif. Binding this same image to "../Images/image2.gif" will create a reference to MyApp\Images\image2.gif. |
Text |
The text to display in the button or link. This applies only to Link Buttons and Push Buttons. Resource File Key You can also dynamically fetch a text string from your application’s resource file (RESX) at application run-time by specifying a Resource Key. This is useful in multi-language applications that have multiple resource files, one for each language. This permits easy application localization by editing your application’s resource file instead of the application itself. Specify the Resource Key in curly braces, e.g.: {Txt:MyTextString} |
Property |
Description |
||||||||||||||||||||||||||||||
CausesValidation |
The data entered into the page is validated by the application. All data in each data entry control on the page is validated.
|
||||||||||||||||||||||||||||||
CommandName |
The particular command to execute upon button click.
|
||||||||||||||||||||||||||||||
CommandArgument |
CommandArgument supplements the CommandName property. The syntax and affects of individual arguments vary depending on various factors, including the URL / Command Name value, the button consumers' properties, table schemas, etc.
|
||||||||||||||||||||||||||||||
ToolTip |
Pop-up help text displayed when an application user moves their mouse over the button. Resource File Key You can also dynamically fetch a text string from your application’s resource file (RESX) at application run-time by specifying a Resource Key. This is useful in multi-language applications that have multiple resource files, one for each language. This permits easy application localization by editing your application’s resource file instead of the application itself. Specify the Resource Key in curly braces, e.g.: {Txt:MyTextString} |
See ASP.NET Control Properties for details.
Your application may contain these properties that are no longer used and are obsolete. In general, most obsolete properties are benign and will not affect your application’s code or run-time operation.
Property |
Description |
||
ControlToValidate |
Specifies the target control to be updated when adding a new record via the Quick Add button feature. ControlToValidate is typically the name of the control of the dropdown list whose value is to be updated after a record is added via a Quick Add button. The database field populating the dropdown list control is specified by the FieldValue property.
|
When a field is bound to a third-party control (e.g, FCKEditor) a postback may be necessary to retrieve the current field value. This is not a problem when page content is saved by clicking the ‘Save’ or ‘Save and New’ button which belongs to page, but it could be a problem for table row buttons. To avoid such problems, Iron Speed Designer adds the ‘PostBack = True’ property to all ‘Save’ and ‘Save and New’ buttons by default.
Properties are declared differently for a Text button (called a ‘theme button’) and an Image button. For example the CommandName property for a text button is Button-CommandName whereas it is just CommanName for an Image button.
The reason is that theme buttons are usually ASCX controls that are included within a page (ASPX). A button component creates a reusable panel and is based on a layout that you can specify. The PushButton, LinkButton and ImageButton are standard HTML buttons. In order to retrieve the property for any ASCX control within a page, it is essential to prepend the name of the ASCX control before the property so that the page is aware it refers to the property of an ASCX control with that name. Image buttons, on the other hand, are simple ASP controls and therefore don’t require us to specify the name of the controls before the properties.
The Button uses several properties to set the values of attributes inside of the Button panel. The properties whose names are prefixed “Button” refer to the attributes within the Button panel. For example, a code generation tag named Button within the Button.html panel is referred by the name Button by the enclosing page or panel. As such, the Button-CausesValidation property refers to the CausesValidation property of the code generation tag named “Button” or “LinkButton” within the ThemeButton.ascx control.
Button Actions - Redirect and Send Email Actions
Button Actions - Substitution Variables
Calling JavaScript Code from a Button