Weird characters when dealing with hyphen

[Greensahil]

I have a barcode that I printed with Dymo label maker that translates to QC-157. But when I tried to scan it in your playground I get:

[onScan]: Code: �QC½157 Quantity: 1

[Greensahil]

If I activate the OnKeyDetect you can see that it is clearly reading some characters wrong. For example it is reading 16 as the first character and there is no ASCII equivalent of 16

It is also reading ASCII 189 for the symbol - which is not true.

My scanner is working just fine because if I open a notepad and try to scan the same code I get:

QC-157

[kabachello]

Hi! Use the keyCodeMapper callback to map the key codes to the desired characters. See example here: https://github.com/axenox/onscan.js#decoding-key-codes.

The trouble is, that the key codes from the JavaScript events depend on a lot of things: the hardware, the operating system, the virtual keyboard used, the keyboard layout, etc. I found, that it practically impossible to decode all codes reliably. Using a custom key code mapper, that deals with the issues of your specific hardware is much easier!

You can also check "keyCodeMapper" in the playground to see how the default mapper works.

[Emsal92]

This worked really well for me
keyCodeMapper: function(e) { return e.key || String.fromCharCode(e.keyCode); },

[Rragen]

Because 16 is the code of the shift key, with the @Emsal92 code I have a weid result with the word "Shift" between each character in the result string. It's the way it recreates an uppercase code ( does lowercase code even exist ? ), for example for the code /123 I had Shift/Shift1Shift2Shift3.

by simply exclude 16 in the keyCodeMapper callback, I have a good result.
keyCodeMapper: (e) => ((e.keyCode === 16) ? '' : e.key || String.fromCharCode(e.keyCode)),

Edit
Excluding 16 was not a good idea, because it results in the weird characters ^^
This stack overflow gives some solutions :

[designosis]

This keyCodeMapper mess makes onscan useless with QR codes.
What a damn shame!