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.
Scout/Proposals/InputValidation
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