Use the SetError method to display the error icon next to the target control and display a specified error message when the user hovers the mouse over the error icon.
This method sets the error description string for the specified control.
This property controls whether the error icon blinks when an error is set.īlinks when the icon is already displayed and a new error string is set for the control.Īlways blinks when the error icon is first displayed, or when an error description string is set for the control and the error icon is already displayed. Use this property to increase or decrease the blink rate of the icon. This property controls the rate in milliseconds at which the error icon blinks. Use this property to change the icon used to indicate an error. In the case where you wish to display different icons or styles, you will need to use multiple ErrorProvider controls.
You can use a single ErrorProvider for multiple controls. Use the ErrorProvider if you want to notify the user that there is an input error by flashing an icon next to the input control. Provides a user interface for indicating that a control on a form has an error associated with it. This time we will look at the ErrorProvider control:ĮrrorProvider Control Last time we took a look at the Timer control. Most of the information about the controls is still applicable to previous versions of PrimalForms. Since the icon and message associated with the ErrorProvider can easily be changed, I figured that would be a good way to create a 'Warning Provider'.
MSDN ERRORPROVIDER HOW TO
(You can set the error to the control by name, or generically by using the sender argument.The “Spotlight on Controls” series focuses on a single WinForms control in PrimalForms 2011, details the important Properties, Methods, and Events of the control and demonstrates how to utilize the control. I have always liked using the ErrorProvider as an easy way to alert the user that something is wrong. If the input is not valid, we set the error shown by the ErrorProvider (the e.Message is generally the same as the Message parameter of any exception that has been thrown). We also clear any errors in the ErrorProvider (not sure of the best way to use this control, but this works). In that event handler, we check if the input is valid (don't know what all that does, but it works - play with it) and, if so, cast the value to the correct data type in order to use for some purpose. The example shows us setting the type of data which should be entered into the text box and then subscribing to the corresponding event. It's really useful when combined with the above data validation method. The ErrorProvider is a WinForms control that allows you to show a red exclamation mark with an error message tooltip next to a control. When the mask is blank, you can accept input just like you can with a TextBox. What you should be aware of, though, is that the Mask is *not* required. If you want to read about the MaskedTextBox, it's all on MSDN. If you do this, as well as subscribe to the TypeValidationCompleted event, on the form Load event, you can handle user validation inside your TypeValidationCompleted event handler. The trick is to set the ValidatingType of the MaskedTextBox control to the type of data you want to get from the user. I just discovered that the MaskedTextBox control allows you to set the type of data which should be entered in the control and helps you do the validation of that data when necessary.
0 kommentar(er)
