I noticed in build 1246, that certain error messages appear BELOW the attribute as shown below:
I asked support about it & they said they are considering putting all error messages here & asked me to seek feedback on the forums.
I think it's a GREAT idea!
Your opinions?
Seeking opinions on error message location
Seeking opinions on error message location
Tom - V8.8 build 3137 - MySql / PostGres
I also agree that the above example looks good, but I wonder how it would look with 2 columns. For example, if Login Name was in column 1 and Password was in column 2. Since Password does not have an error, would it and all fields below it still line up with the fields in column 1.
I have not updated to the current version yet so I can not check this out myself.
I have not updated to the current version yet so I can not check this out myself.
Bob
-
- Posts: 7532
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
The problem is that if this becomes the default behaviour the screen may jump up and down when the user is entering a value - when it's invalid the screen will expand to accomodate for the error message, when it becomes valid, the screen will jump back to normal. Do you find this annoying?
Aware IM Support Team
This is a great improvement! All validation failures must be shown in one screen/shot. Not one at a time like how it used to be before. If the user makes mistake in ‘n’ fields and he/she is not notified in one shot, by this behavior he/she will have to correct the errors one by one and this could be annoying/time consuming as well as unnecessary load on resources
Craig (v4.7 Build 1223)
-
- Posts: 171
- Joined: Tue Jun 16, 2009 12:18 am
Hello,
In our opinion YES the "jumping up and down" would be greatly distracting.
In product scenarios any screen moment for data entry clerks has caused
significantly less efficiency in there workload
i.e. Betty in Accounts Payable has a semi-Heads Down process where as
she must re-key 10's or 100's of documents data.
Every time the screen jumps, her peripheral vision picks this up, and she
looks at the screen thus slowing down her typing and input.
HOWEVER
If we had the ability to MAP keyboard http://www.extjs.com/products/extjs/ with the Keyboard navigation this would resolve what I believe to
be a bad result of the Screen Jumping
In our opinion YES the "jumping up and down" would be greatly distracting.
In product scenarios any screen moment for data entry clerks has caused
significantly less efficiency in there workload
i.e. Betty in Accounts Payable has a semi-Heads Down process where as
she must re-key 10's or 100's of documents data.
Every time the screen jumps, her peripheral vision picks this up, and she
looks at the screen thus slowing down her typing and input.
HOWEVER
If we had the ability to MAP keyboard http://www.extjs.com/products/extjs/ with the Keyboard navigation this would resolve what I believe to
be a bad result of the Screen Jumping