No, the iOS keyboard properties are not redundant... I think that you would
help yourself a lot if you used the UITextfield instead of using a regular LC
field. You can then manipulate the keyboard properties more or less to your
hearts' content...:-)
Dixie
> 1. thanks very much Jacque. I fo
1. thanks very much Jacque. I forgot (if I ever knew) that this preference
exists. There is too much to remember, I find.
2. Looks like it works, tho clunky. I have not yet found out if one can
instantiate an iOS keyboard by script - if not, the latest iOS Release Notes on
setting keyboard prop
On 4/6/12 3:01 PM, Graham Samuel wrote:
Thanks Chris, traversalOn was the answer. Doesn't show up on the
Property Inspector under its own name (I think it's called
'Focusable' which is perhaps slightly more meaningful, but different)
The first thing I do whenever I need to reset my prefs is to
Thanks Chris, traversalOn was the answer. Doesn't show up on the Property
Inspector under its own name (I think it's called 'Focusable' which is perhaps
slightly more meaningful, but different) and I forgot about it. The dictionary
entry explains it well enough, but of course first one has to re
Graham,
I just tried a quick test using a basic scrolling list field, dragged straight
from the tool palette. The keyboard did not appear for me when selecting items
in the field. I noticed that lockText is true and traversalOn is true. Maybe
start there? Otherwise, maybe compare the properties
