btcpayserver/BTCPayServer/wwwroot/js/wallet/wallet-camera-scanner.js

$(function () {
    initCameraScanningApp("Scan address/ payment link", data => {
        $("#BIP21").val(data);
        $("form").submit();
    }, "scanModal");
});
Scan address/bip21 with camera 2020-03-26 11:59:28 +01:00			`$(function () {`
Refactor QR functionality Based on the `ur-registry` upgrade I refactored the `CameraScanner` and `ShowQR` partials: Besides general code changes, the main change is that most of the configuration and result handling now happens on the outer view. Those partials and functions are now generalized and don't know about their purpose (like handling PSBTs): They can be instantiated with simple data (e.g. for displaying a plain QR code) or different modes (like showing a static and the UR version of a QR code) and the result handling is done via callback. The callbacks can now also distinguish between the different results (data as plain string vs. UR-type objects for wallet data or PSBT) and also handle the specific type of data. For instance: Before it wasn't possible to strip the leading derivation path from an xpub when scanning the QR code, because the scanner didn't know about the type of data it was handling. Now that the data is handled in the callback, we can implement that functionality for the scan view only. 2022-08-31 12:27:06 +02:00			`initCameraScanningApp("Scan address/ payment link", data => {`
Remove function checks as they didn't help 2021-01-26 09:40:31 +01:00			`$("#BIP21").val(data);`
			`$("form").submit();`
Refactor QR functionality Based on the `ur-registry` upgrade I refactored the `CameraScanner` and `ShowQR` partials: Besides general code changes, the main change is that most of the configuration and result handling now happens on the outer view. Those partials and functions are now generalized and don't know about their purpose (like handling PSBTs): They can be instantiated with simple data (e.g. for displaying a plain QR code) or different modes (like showing a static and the UR version of a QR code) and the result handling is done via callback. The callbacks can now also distinguish between the different results (data as plain string vs. UR-type objects for wallet data or PSBT) and also handle the specific type of data. For instance: Before it wasn't possible to strip the leading derivation path from an xpub when scanning the QR code, because the scanner didn't know about the type of data it was handling. Now that the data is handled in the callback, we can implement that functionality for the scan view only. 2022-08-31 12:27:06 +02:00			`}, "scanModal");`
Scan address/bip21 with camera 2020-03-26 11:59:28 +01:00			`});`