The component was designed for keyboard wedge scanners, as the component provides dedicated prefix and suffix properties to define scanner input. As such, it can be useful to think of the Barcode Scanner Input component as a specialized text field that does not require focus, and uses characters to decide when to accept and reject text input.
I think the mobile apps have camera barcode scanning though?
I can't find anything about using the camera in the documentation for this component. But the tooltip suggests that? Yes you can trigger a barcode scan on the device, but it seems to be totally unrelated to this component?
Huh, I have to check with somebody who knows better.
I would think this tooltip is wrong/misplaced for this component...
"Enables users to scan a barcode directly from a device's built-in camera."
Yes I suspect that too. Using the barcode scanned Session events makes things a lot more complicated that it should be to just populate a datafield using the built-in camera.
I believe this stems from Perspective being a browser-based technology, which has baked in sandboxing to prevent malicious activity. This makes it harder to directly interact with device hardware; it's not like Vision's JVM.
If you plan on doing a lot of scanning, I recommend using a device that has a built-in scanning engine that can be used with the Barcode Scanner Input component using keyboard wedge mode.
The barcode scan component and the barcode scan action (mobile app only) are entirely separate techniques. Unavoidable, with the way mobile camera scanning is triggered and results accessed.
