I'm getting this error on an application which is scanning multiple QR codes over long periods

Failed to read QR code. Finished up all reserved function pointers. Use a higher value for RESERVED_FUNCTION_POINTERS.

@schmich could you please recompile the script with more pointers as described [here](https://kripken.github.io/emscripten-site/docs/porting/connecting_cpp_and_javascript/Interacti

In order to get it working needs to create also HTML element with specific id. That wasn't mentioned in docs and I was getting error till I made it randomly trying different things.

I frequently re-introduce bugs I already fixed when releasing new features. I always do a lot of manual testing to reduce this but that's annoying and time consuming. I should really learn how to write automated tests but I don't know how to approach this with this component. How to simulate a camera in a test environment?

Stuff I'd like to have covered somehow:

• the component should rende

It's a really simple issue but I think it would be great to define, that the Options for faceMode is of type string. Happy to amend if you guys want!

The material design specs have added a section on the barcode scanning experience. It would be great if the UX could be recreated by this library.

See https://material.io/collections/machine-learning/barcode-scanning.html

My angular cli version details
Angular CLI: 6.2.9
Node: 8.9.1
OS: win32 x64.

On installing the package and including

// Common imports
import { NgModule /* , ... */ } from '@angular/core';

// Import the package's module
import { ZXingScannerModule } from '@zxing/ngx-scanner';

@NgModule({
declarations: [ /* AppComponent ... */ ],
imports: [

    // BrowserModule,

https://en.wikipedia.org/wiki/Patch_Code

In README.md under Usage, function scan (single mode) I'd recommend either wrapping the alert function in a setTimeout as you did in the demo or removing the alert and using console.log. Currently, the alert will not be displayed. This caused me some head thumping until stepped thru a debug and then remembered the demo used the setTimeout.

The module we use (https://github.com/TinyWebEx/AddonSettings) does abstract all the settings of the add-on and by default tries to query the option as a managed option first. Thus, any setting we use, should theoretically be able to be overwritten by an administrator and the user should not be able to change it, afterwards.
The module [for the options page](https://github.com/TinyWebEx/Automatic