Wedge scanner performance issues when lots of barcodes in shot

[timmyhadwen]

When using a wedge scanner in the app there is an issue where if there are multiple barcodes in shot (ie Inventree Label + Digikey or mouser label with N barcodes), high quality barcode scanners will pick up all of them and enter them with new lines in-between.

Inventree ends up trying to handle all of them instead of just the first, meaning the network coms delay results in the notifications appearing over and over again (one for each barcode).

This makes seeing if your barcode actually scanned very difficult as you get 2-3 errors with every success and have to wait 1-2 seconds between scans to let the notification queue clear.

The intended behaviour is that the barcode has a delay after each scan (as configurable in settings) however in this case this delay does nothing.

I propose that in the wedge scanner we ignore characters we receive after the first \n character for the delay time to prevent this queue.

@SchrodingersGat does this sound reasonable?

[SchrodingersGat]

Yes this sounds like a reasonable approach. The scanning pipeline does not support multiple scans, so having a blanking period makes sense

[timmyhadwen]

Great. I'm most of the way there then!