I can do this by checking the content with a procedure after I exit. Or I can ascertain the window/field in a Case structure in a .KeyDown procedure and cobble something up there.
I like to avoid .KeyDown because it bothers me that I’m adding “overhead” to every keystroke.
But there are so many filters already available as data cell “specs” - All Caps, numeric or date, restricted characters, etc. that it seems natural to also - in the same place - be able to specify the maximum number or characters? I guess also the minimum number of characters would be as useful. So that would be two check boxes and fields in attributes; max characters and min characters.
It also seems there are only three basic actions you’d want to take - return to the field with the insertion bar at the front, return to the field with the insertion bar at the back, return to the field with all the content selected.
But you wouldn’t want the user trapped. That is, if you return the user to the field if she leaves it in an invalid state, she may get “trapped”. Let’s say someone clicks into an inventory stock no field and then realizes they don’t have that number just yet. If they click out to another field, and a procedure kicks in determining the field they left didn’t have valid content, and it returns them to said field, then you’d imagine they’d start humming the song, "The Man Who’ll Never Return (to the other database fields) https://www.youtube.com/watch?v=Dh994JcEfkI
I can do the character checking inside my own procedures but I’m wondering if I’m missing something “built-in” to the field attributes in Pan 6 that would do it.
If those character limits are not built into PanX, they’d be a great addition because a “spec” on the number of characters in a field, blends nicely with the other restrictions/auto settings (all caps, etc.) already there.