Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Scout/Proposals/InputValidation"
| Line 11: | Line 11: | ||
=== Forum === | === Forum === | ||
[http://www.eclipse.org/forums/index.php/m/1015825/?srch=execvalidate#msg_1015825] | [http://www.eclipse.org/forums/index.php/m/1015825/?srch=execvalidate#msg_1015825] | ||
| + | Disable OK Button on error | ||
| + | |||
If there is at least one field having errorStatus with severity equals to ERROR, then the Button OK will be disabled. | If there is at least one field having errorStatus with severity equals to ERROR, then the Button OK will be disabled. | ||
-> The "Scout way" is to leave the OK button enabled all the time and rather present a error message to the user when he clicks it. | -> The "Scout way" is to leave the OK button enabled all the time and rather present a error message to the user when he clicks it. | ||
[https://www.eclipse.org/forums/index.php/m/1003550/?srch=execvalidatevalue#msg_1003550] | [https://www.eclipse.org/forums/index.php/m/1003550/?srch=execvalidatevalue#msg_1003550] | ||
| − | + | Limiting input in FormFields, e.g. | |
* suppression of non-numeric input in number fields | * suppression of non-numeric input in number fields | ||
* suppression of digits in string fields | * suppression of digits in string fields | ||
* limiting the number of characters that can be entered in a field | * limiting the number of characters that can be entered in a field | ||
| + | |||
| + | [https://www.eclipse.org/forums/index.php/m/1065592/?srch=execvalidatevalue#msg_1065592] | ||
| + | SmartField.execvalidatevalue cannot be used | ||
| + | |||
| + | SmartField.execvalidatevalue is final | ||
| + | |||
| + | [https://www.eclipse.org/forums/index.php/m/1220946/?srch=execvalidatevalue#msg_1220946] | ||
| + | Not possible to mix execValidateValue and execChangedValue | ||
Revision as of 09:38, 21 August 2014
There have been several issues about the current concepts and implementation of the scout input validation. This page describes the status quo, problems and possible solutions.
Comments
- Validation is done on focus lost or on any key input (getConfiguredValidateOnAnyKey())
Documentation & Discussions
Forum
[1] Disable OK Button on error
If there is at least one field having errorStatus with severity equals to ERROR, then the Button OK will be disabled. -> The "Scout way" is to leave the OK button enabled all the time and rather present a error message to the user when he clicks it.
[2] Limiting input in FormFields, e.g.
- suppression of non-numeric input in number fields
- suppression of digits in string fields
- limiting the number of characters that can be entered in a field
[3] SmartField.execvalidatevalue cannot be used
SmartField.execvalidatevalue is final
[4] Not possible to mix execValidateValue and execChangedValue