|
|
Post by egghead on Aug 18, 2020 15:39:10 GMT
Most of the consumer devices don't have a physical "trigger to press" in order to read an NFC tag. When brought near to a tag, the device continuously reads the tag. However, the requirement is to have a button in the UI on clicking it, only then should there be a read.
What event is to be used to "trigger" an NFC tag read on button press and to prevent a read otherwise?
|
|
|
|
Post by Dmitry Soldatenkov on Aug 18, 2020 20:52:34 GMT
I think, you should read and save(for a few seconds) info continuously but real use stored info only after user press button.
|
|
|
|
Post by egghead on Sept 10, 2020 14:07:00 GMT
Ok, I see the NFC tag read directly from NFC-enabled consumer device is easier to capture than continuous, and sometimes part reads from a bluetooth NFC device such as FEIG RFID BT reader interfaced to a non-NFC enabled consumer device.
A button is therefore not mandatory. I just capture the reads in a read-only textbox in the app whose value is then used to populate a backend database.
In case of FEIG RFID reader however, I have to parse the reads to see whether the tag is partly or fully read before populating the database. But here also, no button required as such.
|
|
