iOS Enter/Return Solution - Cursor Focus Fails To Move After Post
You’re using an RFID-NFC-Barcode reader on iOS that sends [ENTER] or [RETURN] character and after the scan. The scanner/reader you use connects to iOS in wireless keyboard mode. However, you find the focus does NOT move to the next field or next line after the scan. This post shows the iOS Enter/Return Solution for the idChamp RS4x RFID-NFC Reader-Writer. This solution may work for other scanners also.
The core reason that your cursor fails to move after your barcode or RFID reader data is posted to iOS is based on iOS design. iOS is specifically designed NOT to accept any Enter/Return character after your data is posted. It seems the iOS designers wanted to insure use taps something after the data is posted.
Advance The Cursor Focus To Next Field iOS Enter/Return Solution For Browser Apps
You can’t get iOS browser to advance the cursor/field focus after the scan is posted using enter/return character from the scanner.
Native App Submits Data After RFID/NFC/Barcode Scan
You can’t iOS to inherently submit the RFID/NFC/Barcode scan in your native iOS app. This means your iOS app won’t do what you would expect from the ‘Enter/Return’ action character in the scan. As you would expect using a PC for example. Note you don’t have this issue when you use a scanner like the idChamp® RS3x or the NF4x or RS4x in ‘Smart Mode’. Using scanners in Smart Mode your native iOS app will connect to them with the Serial Device Manager (SDM). You only need this iOS Enter/Return Solution when using scanners in HID Keyboard Mode.
RFID/NFC/Barcode Reader Modes
Use use idChamp® family readers in different operation & connection modes depending on your needs. Choose your operation and connection mode options from the table below.
Depending on your scanner, you will have different operation and connection modes. For example you set Keyboard Wedge Mode for 5127ck-mini part using the HID setup tool. Set the Connect Mode between BLE & HID Keyboard using the yACK FAST app.
RS4x Keyboard Wedge Settings
| Reader Model | Reader Mode | Connect Mode | Connect Using |
|---|---|---|---|
|
RS4x |
Smart |
BLE |
Native App |
|
RS4x |
Keyboard Wedge |
BLE |
Native App |
|
RS4x |
Keyboard Wedge |
HID Keyboard |
OS BT App |
|
NF4x |
Smart |
BLE |
Native App |
|
NF4x |
Direct |
BLE |
Native App |
|
NF4x |
Direct |
HID Keyboard |
OS BT App |
|
RS3x |
Direct |
BLE |
Native App |
|
RS3x |
Direct |
HID Keyboard |
OS BT App |
|
DX1 |
Direct |
BLE |
BLE |
|
DX1 |
Direct |
HID Keyboard |
OS BT App |
By default 5127ck-mini component of the RS4x has the “Poststrokes” set to “[ENTER]”. You’ll find this won’t work when the RS4x is in HID Keyboard Connect Mode because iOS does not support Enter/Return. You set the Poststrokes to a character your native iOS app will identify as the end of the scan data. Your app will use this character ‘as the Enter value’ to submit the data. One common value native iOS apps use to signify the end of scan data is CTRL-J. You specify this in the HID tool using “[CTRL]J” as shown below:
Native App RFID Scan Posting
Your native app sees CTRL-J as LINE FEED and uses this character to identify the end of posted data to submit. This is your native app iOS Enter/Return Solution when using HID Keyboard Mode on iOS. Additionally native apps on other platforms e.g. Android you specify LF as your ‘end-packet-flag’
