Hi everyone!
I have a user that's reported a bug that I'm not sure how to resolve. They have stated that they cannot switch between two text fields, and continue to type (for example, click into field user, and then click to field password).
the work around they've found is clicking on a text field and entering the information, clicking out of said text field, and then clicking into the other text field that they are looking to input information into. They have noted that this will indeed work, but obviously this is not ideal.
this issue seems to be isolated to this individuals device. They are running on a Samsung S5, and using Android Version 5.0.
I have reached out to the testers using early versions of android, and different devices, and so far none have reported this issue.
I wondered if anyone else may have run into this issue, would have any ideas on how i would go about fixing this, or any resources that may be helpful.
Thanks in advance!
-Sean
Bug/glitch reported by Android test anyone else seen this?
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: Bug/glitch reported by Android test anyone else seen thi
Do you use native android fields or normal fields?
Livecode Wiki: http://livecode.wikia.com
My blog: https://livecode-blogger.blogspot.com
To post code use this: http://tinyurl.com/ogp6d5w
My blog: https://livecode-blogger.blogspot.com
To post code use this: http://tinyurl.com/ogp6d5w
Re: Bug/glitch reported by Android test anyone else seen thi
Hi Max,
Thanks for getting back to me on this.
The version they are testing right now is using normal fields, but I am looking to switch to native in a coming update. I was wondering if that could be part of the issue, but wasn't 100% certain.
I did get an update from the tester with the issue, and they've been using a specific keyboard called "Swype" on their S5. They have since switched back to the default keyboard when doing this the issue disappears entirely.
I'm wondering if this is any indication of an issue cause by not using native fields, and hope to have more of an idea on this once the update has been pushed, and I get feedback from the testers.
-Sean
Thanks for getting back to me on this.
The version they are testing right now is using normal fields, but I am looking to switch to native in a coming update. I was wondering if that could be part of the issue, but wasn't 100% certain.
I did get an update from the tester with the issue, and they've been using a specific keyboard called "Swype" on their S5. They have since switched back to the default keyboard when doing this the issue disappears entirely.
I'm wondering if this is any indication of an issue cause by not using native fields, and hope to have more of an idea on this once the update has been pushed, and I get feedback from the testers.
-Sean
Re: Bug/glitch reported by Android test anyone else seen thi
I'm guessing that native fields would solve this because they interact directly with the OS for keyboard responses. LC fields have failed for me in the past with some third party keyboards.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Re: Bug/glitch reported by Android test anyone else seen thi
Native field are always to prefer to normal field when user needs to write inside them. Android automatically change the keyboard layout if more the one field is present, on the keyboard appear the button next to switch to next field and in the last field appears enter. Native field are fantastic with user input.
Livecode Wiki: http://livecode.wikia.com
My blog: https://livecode-blogger.blogspot.com
To post code use this: http://tinyurl.com/ogp6d5w
My blog: https://livecode-blogger.blogspot.com
To post code use this: http://tinyurl.com/ogp6d5w