I am using Socket IOS SDK with 7xi scanner. The scanner is fast enough to register a duplicate scan in quick succession if the user keeps the barcode in front of the scanner in the user's standing mode. To handle this, when I scan for the first time, and by the time I'm not ready for the next scan, I'll remove my scan representative.
Of course, the scanner only issues scanning, is there any way to silence the beep when I'm scanning, so that my users do not understand that the scan was properly received when the app was not there . It should be fast enough that I can re-enable it on the second or the other.
background
the scanner has three confirmation modes (devices, SDKs and apps) ) That determines who was responsible for accepting the barcode was scanned. The default device, which will accept any successful scan (i.e. the barcode type is supported and the device has successfully decoded the barcode).
Solution
Option 1
Currently, you remove the scan representative, which does not prevent the scanner from scanning the next barcode; This only prevents your app from receiving event notifications. You provide Scan Apihahler with a timer routine which checks the new event to call doReceive and if it detects that it calls your representative.
You can add a flag to your timer so that it will call only doReceive when you are ready to handle the next event.
This approach has two limitations, if an important information is given on the device, then there will be a delay between the device's acceptance and response when a scan is conducted in Qi. Second, a queue activity is only suitable to handle a small burst, but downtime will be required to withdraw your application.
Option 2
Warning: I'm not sure that it works in presentation mode
Confirmation mode switch to app Please accept the barcode after processing your application. It takes advantage of the closing of your scanner (it will not beep, flash or vibrate for any scan) until your app has received the barcode.
The downside here is a small gap between the scanner while reading the barcode and accepting it while using App Confirmation Mode. Adding an additional delay while processing data processing can not be the best user experience.
No comments:
Post a Comment