navcoin-core
navcoin-core copied to clipboard
navcoin
Navcore 6.0 Possible Display Bug On Windows 10
Reported by user:
Navcore 6.0 Possible Display Bug On Windows 10: While operating a 2018 Lenovo 920 Yoga Laptop, with the display is set at 3840x2160 (shows as "recommended" setting) and the size of the text and apps is set at 300% (also "recommended" setting), the seed words to create a new wallet do not show. To correct this the user has to close the installation and change the text size setting from 300% to 100% (very very small font)... it is very unlikely that a user would select those settings. Even at 200% the seed words are cut-off (partially see the letters in the words). Might be a good idea to correct this.
Is the text issue only on the seed step? Or on the whole wallet? I remember fixing a font size issue before on the home screen of the wallet.
On Sat, Jan 30, 2021, 00:49 alex v. [email protected] wrote:
Reported by user:
Navcore 6.0 Possible Display Bug On Windows 10: While operating a 2018 Lenovo 920 Yoga Laptop, with the display is set at 3840x2160 (shows as "recommended" setting) and the size of the text and apps is set at 300% (also "recommended" setting), the seed words to create a new wallet do not show. To correct this the user has to close the installation and change the text size setting from 300% to 100% (very very small font)... it is very unlikely that a user would select those settings. Even at 200% the seed words are cut-off (partially see the letters in the words). Might be a good idea to correct this.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/navcoin/navcoin-core/issues/769, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIDAKPENJVUN7WIPPFPGVLS4LRK5ANCNFSM4WZE7LGA .
reply from the user:
It's in the step where it asks users to write down the seed words and in the step where the user is asked to enter the seed words as confirmation. I don't remember seeing it in the prior steps.
I saw another user mention this issue on discord, I'll see if I can't get a PR that fixes this ready