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
Question, so the menu there if you see in your screenshot the white dividing line from the list and the information for each corresponding tab, there is a scroll bar there, depending on resolutions/screens it can be difficult to see either or.
I will look into maybe another color for the scroll bar as this is more than likely a size issue, not sure if reorganizing the list would be better.
On Fri., Jul. 3, 2020, 10:37 a.m. Liquid369, ***@***.***> wrote:
Question, so the menu there if you see in your screenshot the white
dividing line from the list and the information for each corresponding tab,
there is a scroll bar there, depending on resolutions/screens it can be
difficult to see either or.
I will look into maybe another color for the scroll bar as this is more
than likely a size issue, not sure if reorganizing the list would be better.
General flows is a debug as last
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dogecash/dogecash/issues/51#issuecomment-653552915>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADMWXAHF7EKSAB4LTB7EHLRZXNKXANCNFSM4OPZ63AA>
.
The first time you access the settings menu after restarting the QT wallet, the debug menu is not visible.
Can you reliably reproduce the issue? Yes
If so, please list the steps to reproduce below:
Expected behavior
Debug options menu should be visible
Actual behavior
Debug options menu is not visible until another menu is clicked
Screenshots.
If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
What version of DogeCash Core are you using?
v5.2.1.0-0a7cf1c95-dirty
Machine specs:
Any extra information that might be useful in the debugging process.
This is normally the contents of a
debug.log
,db.log
orconfig.log
file. Raw text or a link to a pastebin type site are preferred.debug.log attached. db.log is empty, config.log does not exist.
debug.log
The text was updated successfully, but these errors were encountered: