Post by tao on Aug 18, 2015 7:16:02 GMT
This is mostly due to the verification of EditBox.SetTextValue().
In the early stage, the SetTextValue() and SetUnverifiedTextValue() are the same; SetTextCharacters() and SetUnverifiedTextCharacters () are the same, but in fact they should be different as stated in safsdev.github.io/sqabasic2000/EditBoxFunctionsIndex.htm.
- SetTextValue() will handle the special key like ~^+%{( , and will be verified if what we inputted are the same as what we want to input. [One more thing: when the input information contains special key, SE+ will not verify its property.]
- SetUnverifiedTextValue() are almost the same as SetTextValue() except it will not verify its property.
- SetTextCharacters() will not handle any special key. It will treat all the inputting information as the plain text. Also, it will be verified if what we inputted are the same as what we want to input.
- SetUnverifiedTextCharacters() are almost the same as SetTextCharacters() except it will not verify its property.
So, mostly you may want to just input the information without any verification. In this case, you can use SetUnverifiedTextValue() instead.
If you do not want to deal with the special key, just want the plain text, using SetTextCharacters() or SetUnverifiedTextCharacters() instead.
If you do want to be verified and see the failure information, please double check, when you run your testing, do you move the cursor which will lead to set the focus at another place? Moving focus will make the inputting information in wrong sequence.