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).
On Fri, May 30, 2014 at 6:39 PM, Angel Leon gubat...@gmail.com 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
On Mon, Jun 2, 2014 at 12:39 AM, Wladimir laa...@gmail.com 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
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;
-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.
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
6 matches
Mail list logo
