Not detecting barcodes without successful scan
See original GitHub issueThank you for taking over maintainership of this package!
I noticed the live_w_locator example has changed behavior between versions 0.0.2 and 0.0.3. Earlier, the scanner was painting green squares when it started noticing barcodes without successfully scanning them, i.e., onDetected
callback is not called. Now, the green squares are only painted when a barcode is successfully scanned. So it seems the content of result.boxes
for the Quagga.onProcessed
callback behaves differently after version 0.0.3. Is this a regression?
To reproduce
- Compare the old behavior on https://serratus.github.io/quaggaJS/examples/live_w_locator.html to the live_w_locator example in master branch
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Why Aren't My Barcodes Scanning? 3 Common Problems ...
If your scan issues aren't consistent, or you can otherwise confirm your scanner is set-up to read your barcodes, you may not be...
Read more >When a Verified Barcode Fails to Scan-What To Do
If the verifier says the barcodes are good but the scanner cannot read them, check the scanner configuration for barcode data field size...
Read more >The Most Common Causes of Unreadable Barcodes
For seemingly high-quality codes, it is a common misconception that no-read results are due to obscure or undetectable barcode characteristics that the reader ......
Read more >Having Problems Reading Your Barcodes? Here's How to Fix It
Poor label placement. The most obvious culprit of an unreadable barcode is poor label placement. · Poor barcode/scanner position. A failed ...
Read more >Barcode Scanner Troubleshooting - Labeling News
Barcode scanner not working? Here's some quick tips to try.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you Erik for the fix! I can confirm that it works.
Lessons learned today:
0.0.6 should fix this issue