Difference between revisions of "Scout/Proposals/InputValidation"

Latest revision as of 06:25, 19 March 2024

The Scout documentation has been moved to https://eclipsescout.github.io/.

@@ 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 ===
-[http://www.eclipse.org/forums/index.php/m/1015825/?srch=execvalidate#msg_1015825]
-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]
-Limit user input, 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