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
krumblez opened this issue
Feb 6, 2019
· 1 comment
Assignees
Labels
FeatureFeature request, user suggestions and enhancements whic are not part of any milestoneGUIEverything related to graphical user interfacemintingEverything related to mintingquestionFurther information is requestedrandom issueRandom issuexionxION related
On new client 3.1.0 the privacy window displayed autominting enabled but on the bottom client indicators is showed as disabled, upon further inspection int he options I saw that 'Enable Automint Addresses' was enabled (as it is by default) - this is a little confusing, or could be for some of our users.
If Zerocoin is disabled in the options / .conf, it should show as disabled fully and not to give different messages in the GUI.
Confirmed by another team member.
3.1.0 - Win 64
Windows 10 Pro, Dual Xeon E5-2637 @3.5GHz
The text was updated successfully, but these errors were encountered:
raid12345678
changed the title
Automint showing as enabled on Privacy page when .conf and settings are set othewise
[GUI][xION][Minting]Automint showing as enabled on Privacy page when .conf and settings are set othewise
Mar 1, 2019
FeatureFeature request, user suggestions and enhancements whic are not part of any milestoneGUIEverything related to graphical user interfacemintingEverything related to mintingquestionFurther information is requestedrandom issueRandom issuexionxION related
On new client 3.1.0 the privacy window displayed autominting enabled but on the bottom client indicators is showed as disabled, upon further inspection int he options I saw that 'Enable Automint Addresses' was enabled (as it is by default) - this is a little confusing, or could be for some of our users.
If Zerocoin is disabled in the options / .conf, it should show as disabled fully and not to give different messages in the GUI.
Confirmed by another team member.
3.1.0 - Win 64
Windows 10 Pro, Dual Xeon E5-2637 @3.5GHz
The text was updated successfully, but these errors were encountered: