You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This request originated from a Seedsigner user (actually multiple users) requesting/suggestion that the QR code backup functionality display all 4 registration boxes of 25x25 and 29x29 QR codes the same. It looks like Seedsigner is using the CircleModuleDrawer() output option, and no other built-in options here quite solve the UX issue. At present, the three main boxes have a distinct square pattern and the bottom right is displayed as dots.
Target area:
Real life screenshots:
This is a very minor point but given that multiple users have noticed/complained about this over the last year, it felt prudent to highlight as an enhancement request here. A less confusing user experience when transcribing QR code backups by hand using the seedsigner would be for all 4 registration boxes to have the same appearance, distinct from the dots of the user-specific data.
The text was updated successfully, but these errors were encountered:
This request originated from a Seedsigner user (actually multiple users) requesting/suggestion that the QR code backup functionality display all 4 registration boxes of 25x25 and 29x29 QR codes the same. It looks like Seedsigner is using the CircleModuleDrawer() output option, and no other built-in options here quite solve the UX issue. At present, the three main boxes have a distinct square pattern and the bottom right is displayed as dots.
Target area:
Real life screenshots:
This is a very minor point but given that multiple users have noticed/complained about this over the last year, it felt prudent to highlight as an enhancement request here. A less confusing user experience when transcribing QR code backups by hand using the seedsigner would be for all 4 registration boxes to have the same appearance, distinct from the dots of the user-specific data.
The text was updated successfully, but these errors were encountered: