Not on testnet. v5.0.0.0-g19e30fa7e-0. Running wallet as Administrator. Win 10 Home.
When I click on 'send' and the wallet sending window opens, the pointer jumps to send button to save time I guess. When I close it and then click on another main menu option on the left, the pointer still jumps to where the 'send' button was. @jamescowens Link to video coming... https://vimeo.com/458575905
That isn't going to work posting a bug this way. Please put a proper title and an independent description in. Links to Slack archives do not work for all people and are perishable. I want the GitHub record to stand on its own.
Hmm... very interesting. I can't duplicate the behavior on my Windows node. @barton2526 can you try?
Does this persist when you restart the wallet and/or restart the computer and the wallet? Any special settings with the mouse?
I will make time to do a little matrix of variable conditions, hang on, 2
days probs :-)
On Thu, 17 Sep 2020 at 04:51, James C. Owens notifications@github.com
wrote:
Does this persist when you restart the wallet and/or restart the computer
and the wallet? Any special settings with the mouse?—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gridcoin-community/Gridcoin-Research/issues/1889#issuecomment-693791931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQDXZZHI7HTKQFPE7OE73DSGGBUNANCNFSM4RN2VSRA
.
Sounds good. :)
@philipswift I am very interested in figuring out how to trigger this and fix it. Did you get it to happen again, and if so, what conditions triggered it?
Well it did not stop doing it. I checked just now and it is still doing it.
It could be related to MS C++ redistributables. We had issues with that in
2014! I have a lot of them installed.
I'll do a fresh cloud non testnet node, and also do an uninstall of C++
redis' one by one.
PS: UCT time is not the correct time for me in the UK in the summer. Just a
wish list thing really with all the other priorities. The only
scenario would be using time stamps when communicating about
issues/troubleshooting and UK residents in Summer that like to see the
right time in all cases. Possibly when comparing time stamps from the GRC
wallet with other software such as the BOINC log which may takew the time
from the node not the server or elsewhere.
On Thu, 24 Sep 2020 at 12:57, James C. Owens notifications@github.com
wrote:
@philipswift https://github.com/philipswift I am very interested in
figuring out how to trigger this and fix it. Did you get it to happen
again, and if so, what conditions triggered it?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gridcoin-community/Gridcoin-Research/issues/1889#issuecomment-698297538,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQDXZYCRUOLYB37HCHQYKDSHMX3DANCNFSM4RN2VSRA
.
the BOINC log and the console ALWAYS use UTC. currenttime is a console command, so it outputs in UTC. That was my point. The UI reports in local time.
Let's definitely track this mouse business down...
Don't start the mouse jokes ;-)
On Thu, 24 Sep 2020 at 16:11, James C. Owens notifications@github.com
wrote:
Let's definitely track this mouse business down...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gridcoin-community/Gridcoin-Research/issues/1889#issuecomment-698407662,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQDXZY6DGDMHWT2TI2M7BTSHNOR7ANCNFSM4RN2VSRA
.
This can be closed. It is down to a corrupted user profile and classed, unspecifically, as a 'known issue' when changing between using 'Local Account' and signing in on the device, with a Microsoft Account. Refer to Microsofts https://support.microsoft.com/en-us/help/14039/windows-fix-corrupted-user-profile.
Most helpful comment
That isn't going to work posting a bug this way. Please put a proper title and an independent description in. Links to Slack archives do not work for all people and are perishable. I want the GitHub record to stand on its own.