Test Case #2
Note: While following the instructions clicking on the wallet icon in the top left did nothing for me. I never saw anything to click "generate new address" and I never got to see the 10 seed words. I had to log out and log back in and then my address was already populated. Also, I don't see any spot to create my nickname?
Q1. Transaction was successful and credited the correct amount in unchained (77777.00)
Q2. Transaction was successful (showing in core wallet instantly) and unchained decreased by the correct amount (7777.00) + 3.34 was this a fee?
Test Case #3
Video Name: Sunset
Nickname: NA (I can't find where to change it?? I'm looking under "My User Record")
TestNet Biblepay balance: 69996.66 BBP
Please tip whenever convenient.
Extra note: the client has crashed a couple of times immediately after opening but either re-opening or restarting my computer seems to fix it..
1) Great testing, your getting through a lot of this.
2) Regarding the seed words, the nickname and all that: First of all, I took out Seed Words, took out Generate new wallet, and Recover; so all that is gone. Now when you create an account, we create a bbp address for you (this is to simplify it for the user).
To set your nickname, just log in again, and navigate to My User Record; then set it and save it. If you could please test the 2fa features, that would be nice also.
3) I See your video: I tipped you 70K. You should have it now.
4) Regarding the fee: I explained this earlier in the testnet thread on one of the posts.
5) Regarding the crash: Could you please try to reproduce it again: Try starting from a clean environment, by deleting everything but your wallet in this directory:
%appdata%\biblepay
If it is not reproduceable, try 5 times in a row-- at that point Im going to assume its the Dash 'new css bug' which is cleared up once you boot the client once and set your default settings.
I dont think that is going to be an issue in prod, because we have the qt settings set when you transition, and new users get that key set for them once...
However if you can reproduce let me know the circumstance.
Otoh, if you think its related to low-resolution (IE if your monitor is less than 1024x768) let me know, that is another possibility (because this crash is related to either CSS being set the first time, we have one called bezaleel and its saved as DARK, OR the font pitch size).
Im using windows, linux, and MAC and no longer seeing a crash.