Auto Complete in Mobile App

[devinst]

Are there any know issues with using an textbox defined with a database driven auto complete option in a mobile device app?
I do not get any auto complete suggestions until I enter 5 characters. When I run the same program by launching a session on the web page, I start getting suggestions with the first key stroke.
I thought it may be a delay but I tried waiting a while after the first and second key strokes I still got nothing. And when it does start making suggestions it is fast.

Thanks.!!

[Scott Klement]

I just ran a quick test, and had no problems. I hit one key, and it immediately showed matching rows.

Is it possible that your database access is slow? If so, the time it takes to retrieve all rows matching just one key might be much longer than the time to match 5 keys. Therefore, you could have time to type all 5 before something shows up. This is just a wild guess, it may be 100% wrong.

[devinst]

Hey Scott. I thought of that so I did a couple of test.
1. Directed the textbox to a table that only had 5 records in it. Same result.
2. Entered the first letter and waited 5 minutes. Never came up.
3. Exited the program and redirected the text box to the large table. Then once back in, I started typing. Nothing until I typed the 5th character. At that time, the list popped right up.
Once the list is up, if I start back spacing though, the list adjust according to the changes made in very good time.

Just found a new bit of info to throw in. I have tried it on 2 different android devices and got the same results. However, when ran on my iPhone, it works fine. So it does seem to be something with the device.

Something else I discovered. The format for this field is 4 alpha and then numeric. When I type one alpha character and then a number, if I backspace I get the list according to the first letter. It is acting like it is not seeing anything until the first number is entered. Along those same lines, I am using a transform to uppercase on the textbox. The alpha characters in the database are upper case. I did try typing the characters in uppercase on the device but that did not seem to help.

Lots of info, I know.....

Thanks.!!

[Scott Klement]

Well, I found this... it's not exactly the same issue you're having, but it is very similar:
https://bugs.chromium.org/p/chromium/is ... ?id=118639

Basically its saying that the Android version of Chrome is not sending keyboard events to applications. They feel that as soon as they send the keyboard code, they can no longer do stuff like "auto correct" or predict what the user was typing and offer suggestions.

I have no way of knowing if that is what you're experiencing or not, but it makes sense. When you get to the point where you're typing a number, it becomes clear to Chrome that you're not just mispelling a word, and at that point it signals the application that you've actually pressed the keys. Prior to that, it's not signalling the keystroke because it thinks you might change what you've typed.

I didn't see the problem on my device because it's not Android. (My mobile devices are all Apple devices.)

I would recommend that you file a support ticket with Profound Logic. They can try this on Android devices and see if I'm right. They can also do better research into what the cause is, and see if there's a way things can be changed to make them work better.

To file a support ticket, e-mail support@profoundlogic.com.