|
|
(6 intermediate revisions by the same user not shown) |
Line 1: |
Line 1: |
− | 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.
| + | The Scout documentation has been moved to https://eclipsescout.github.io/. |
− | | + | |
− | == Comments ==
| + | |
− | | + | |
− | * Validation is done on focus lost or on any key input (getConfiguredValidateOnAnyKey())
| + | |
− | | + | |
− | == Documentation & Discussions ==
| + | |
− | | + | |
− | [[Scout/Concepts/ValueField#Events | ValueField#Events]]
| + | |
− | | + | |
− | === Forum ===
| + | |
− | [https://www.eclipse.org/forums/index.php/mv/msg/796057/1403082/#msg_1403082]
| + | |
− | | + | |
− | | + | |
− | [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.
| + | |
− | -> 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]
| + | |
− | 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
| + | |
− | | + | |
− | [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
| + | |