I'm generating a screenshot slideshow similar to the steps described in #426 ... oddly today I started getting an error:

Setup: Win7x86
Steps:

1. Grab some screens of various sizes with Greenshot
2. Load into STG, add a progress bar and a watermark
3. Save as weither GIF or APNG

Defect:
![2019-03-02 22_17_11-exception viewer](https://user-images.githubusercontent.com/1289134/53690914-f7

Summa

The Windows install FAQ is likely very outdated, since it looks like a good portion of it involves installing things necessary for RMagick to build:

https://github.com/mroth/lolcommits/wiki/Installing-on-Windows

Since we got rid of RMagick long ago (years even?) some of these steps are probably unnecessary now.

Can you add button click border color option separately for buttons.

The border icon is perceived as an checkbox icon because it is very similar to the checkbox icon.
I think It may be a different icon or no icon.

Damn. Is there any one who can clearly explain below two lines???
link

matches = truths[best_truth_idx]          # Shape: [num_priors,4]
conf = labels[best_truth_idx] + 1         # Shape: [num_priors]

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

https://hosted.weblate.org/zen/webcamoid/main/nb_NO/?type=nottranslated

Could all these strings be explained? I feel annotating these strings would result in higher quality translations. It is also possible for admins to add screenshots.

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!

to help with unit tests, be able to turn off the text on the patterns. This will provide known image for testing inputs, testing loopback, and testing outputs (like the encoder).

I can see a case for leaving some of it on, but I would prefer the option of having the same image across all everythings. The case for testing for text on an image doesn't seem worth the effort in providing a UI/A

Move the gh-pages code inside a docs folder on the master branch and configure Github to automatically publish this folder when a modification occur. This will give more flexibility when updating the demo site.