On the desktop activity view the prices are right aligned but due to
adding fiat prices this means that the bch amounts are not lining up.
This adds a little space between the two in order to make them much more
readable.
This actually reads all the raw transactions from disk in order
to parse the outputs and compare it with the user typed address.
To my surprise, it's actually fast. 4000 transactions took 26ms
to filter.
This widget is only used by the desktop, so no point in storing it in
the Flowee Subdir.
It basically turned out that it is so simple to do this that mobile got
its own more specilistic version.
This now has a bit of a jittery bahavior when we're waiting on the
network and maybe to find some peers.
Going back to normal smooth progressbar behavior as soon as one block
has been downloaded.
This removes Qt bug workarounds for a the old 6.5 we no longer use on
mobile.
This adds a new workaround for CHF as that somehow no longer has a
'symbol' set, so now we provide our own.
Also make sure we run a fetch when the user changes the currency.
This uses the strategy to create one transaction per utxo instead of one
per address which makes this module actually provide some usefullness to
such wallets.
This shows the amount of coins stored on a single address, which we
sweep in one transction by default for privacy reasons.
This adds the ability of the user to specify how many outputs a single
transaction should have when we create it.
The idea is that if you send a transaction you may want to see it
getting confirmed.
This now shows directly in the main UI in an unobtrusive manner with
checks.
Instead of pre-allocation, this moves it to just before we actually
broadcast.
This solves a possible failure of detecting target funds in case the
number of transactions is larger than the gap and the user sends only
one or two of the later once instead of all.
This makes the widgets more re-usable by following the general
design of Qt components with porperties like implicitWidth being
implemented as expected.
When a transaction has been created by the plugin, this stores it also
on our UI classes and forwards the broadcast status for the front end
to use in some animation.
Following the moving of this to the 'explore' tab as "find more"
this is more a detailed listing of all modules, and as a result it
makes sense to add an 'open' button.
This avoids people being forced to enable a feature they only want
to use once.
Following this new UX the 'ON' ribbon loses its meaning, you can
use a module that is not on.
I mean, yes, the fancy enums help readability, but the fancy enums
actually pull in a rather large dependency that adds hundreds of
kilobytes to the deployment. Then just ints don't look so bad
anymore, do they?
This section type means that the module will have it's icon shown in
the 'Explore' tab always, it can not be disabled by users and as such
it just becomes an overflow of the main app avoiding worry about a
module not being found.
This moves the decision if it is importing out of the wallet and we stop
using a broken heuristic.
Also cleanup the API usage of the hd masterkey format in the wallet
header.
tomFlowee