Great! I have a vague memory of trying to have a transparent entry field so
that it could show some faint placeholder text when empty then change to opaque
when any text was entered, and not being able to get it to work.
Terry...
On 27/11/19, 2:39 pm, "use-livecode on behalf of J. Landman Gay
Found it, it was the alpha. When I leave that out, it displays, is
editable, and works.
Thank you!
On 11/26/19 8:16 PM, Terry Judd via use-livecode wrote:
I primarily use single line input fields on my apps' login screens. Here's what
I do for a password field - for a 'normal' field I just ch
I primarily use single line input fields on my apps' login screens. Here's what
I do for a password field - for a 'normal' field I just change the
'contentType' to 'plain'.
mobileControlCreate "input", pControlName
mobileControlSet pControlName, "rect", the rect of pObj
mobileControlSet pControl
Thanks Terry. I keep finding new things. It turns out my multiline fields
are working, but the single input ones do not. Very strange.
Do you have single line inputs?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On November 26, 2019 5:
Not sure if it will help, but here's the code I use to create a multiline text
control (pControlName) on iOS that 'overlays' an existing LC field (pObj)
# create a native multiline text control
put the rect of pObj into tRect
# shrink the rect by 1 pixel all around to reveal the object's border
a
I have reduced the problem to iOS input fields. Some testing shows that:
* The native fields exist
* Their rect is correct
* If I script their text data, it is there and can be retrieved
But they are inactive, can't be tapped, don't show any text even if its
entry is scripted, can't be typed in
Thanks Panos. Resetting didn't work, so now I'm wondering if it is
something about my LC native fields. The first thing the user needs to
do is log in, and I can't test beyond that until I can enter
credentials. There are two native fields, both are transparent. Would
transparency in iOS matter
Hello Jacque,
So the iOS standalone is installed to the iOS simulator, but the simulator
does not respond to clicks / keyboard entry?
I am on Mojave as well, but have not seen that happening.
Maybe it is worth resetting the simulator state:
Quit any instances of Xcode and iOS simulator, and exec
When I run a test on the iOS simulator, it will not respond to either
clicks/taps or keyboard entry. Basically, it's inert. I've tried several
different hardware devices, all with the same results.
A Google search seems to show that this is a bug in the simulator when
running under Mojave, and