Re: [Bitcoin-development] [QT] Feature proposal: Displaying current Units/Changing Units with status bar control.

2014-06-02 Thread sebastien requiem
Hello Angel, Good initiative. This looks good. If I understand, the dropdown menu is for the whole application, so it make sense to have it in a common part of the layout. A slight optimisation would be to write the unit in the transaction table header too (since we read from top to bottom). This

Re: [Bitcoin-development] [QT] Feature proposal: Displaying current Units/Changing Units with status bar control.

2014-06-02 Thread Wladimir
On Fri, May 30, 2014 at 6:39 PM, Angel Leon wrote: > > Here's how it looks (see attachment), just wanted to get feedback, if this > is something you also consider valuable in terms of user experience, or > maybe you don't want to allow any more controls on the status bar (because > then people wil

Re: [Bitcoin-development] [QT] Feature proposal: Displaying current Units/Changing Units with status bar control.

2014-06-02 Thread Gregory Maxwell
On Mon, Jun 2, 2014 at 12:39 AM, Wladimir wrote: > If that is done, I'm not sure how much a global setting in the status > bar would add. It may make it more apparent to the user that multiple > units can be selected. If thats done it should be done in a way in which it's impossible that a stray

Re: [Bitcoin-development] [QT] Feature proposal: Displaying current Units/Changing Units with status bar control.

2014-06-02 Thread Angel Leon
With this I'll continue then to work on this with the addition of: - Showing the current unit on the header column title "Amount ($unitHere)" - Will make sure the user cannot change the current unit of display by mistake by adding a confirmation dialog. Thanks all for the feedback! Angel. http://

[Bitcoin-development] Another uninitialized memory problem

2014-06-02 Thread Toshi Morita
I'm seeing another uninitialized memory problem in bitcoind using valgrind: tm@tm-VirtualBox:~/bitcoind/bitcoin/src$ valgrind ./bitcoind ==2337== Memcheck, a memory error detector ==2337== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==2337== Using Valgrind-3.8.1 and LibVEX; rer

[Bitcoin-development] Lets discuss what to do if SHA256d is actually broken

2014-06-02 Thread xor
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I thought a lot about the worst case scenario of SHA256d being broken in a way which could be abused to A) reduce the work of mining a block by some significant amount B) reduce the work of mining a block to zero, i.e. allow instant mining. B

Re: [Bitcoin-development] Lets discuss what to do if SHA256d is actually broken

2014-06-02 Thread Luke Dashjr
On Tuesday, June 03, 2014 4:29:55 AM xor wrote: > Hi, > > I thought a lot about the worst case scenario of SHA256d being broken in a > way which could be abused to > A) reduce the work of mining a block by some significant amount > B) reduce the work of mining a block to zero, i.e. allow instant m