I found in the version notes that in 3.5.3 (i think) Servoy was changed so the user cannot leave a field into which s/he has entered incorrect data type – like text in a number field, or simply trying to put a $ in a number field… This was to be a feature, and i see why it seemed necessary – previously the red would jump around the screen as the user clicked around. Am I the only one getting VERY confused users reporting that Servoy has crashed? They don’t SEE the red, and if they do notice it (though not one has mentioned on the phone that the text is red) they don’t know what it means. So they task-manage end the servoy session, or force quit it, and then go back in and make the exact same mistake. I have had more than 3 users tell me Servoy is broken when they use a number field on a particular screen, only to discover when I come watch them that they are typing a $ into a number field and getting trapped in the field with no idea why. They see this as a crash.
No one else having this problem? If not, I really need a way to disable this feature… This isn’t a training issue for us – it’s too specific for people to remember. At the very least could the status text in the lower left say “text entry incorrect” or somesuch the way Servoy does when someone tries to type in a field that has no record created yet… Trapping the users is not translating to them as a gentle hint that they shouldn’t type a $.
Also, if you accidentally type $123. Hit backspace or delete to clear the field. now type 123. It still doesn’t accept it. If you go 1234, now it accepts it because it is different than the numeric part of the original entry.
This is pain because they cleared the red with a valid number and it still won’t accept it.