This adds the ability to paste an almost correct seed phrase, for
instance when the last word is cut off.
We also provide a new UI to propose words while typing the seed,
allowing the user to tap on the words instead of having to finish typing
them.
This changes the notes property to be only set by the user of the
BroadcastFeedback.qml, and not from inside anymore which could break the
property binding causing strange things to happen.
When the user has had the screen locked long enough to make the app
lock, we just close the popup.
The unlock screen actually appears under popups (that's the concept of a
popup..) so this solves a leakage of data.
This is the only useful notification type we have today,
but at least it allows the user to explicitly go and request
notifications from the Android OS.
Use the new TextButton feature better for current setting
and make clear in the sub text which wallet this is for.
On the send tab the InstaPayConfigButton is directly next to the
default wallet, as such it may be assumed that the insta pay
text applied to the name mentioned there.
This lists the wallet here in order to make things clear and
now lists the actual limit on the right side for consistency.
This swaps the colors on the AccountHistory and ExploreModules
rounded rects in order to make the background universally the same
everywhere.
To make it work the 'light' color on the light theme had to remove
some of its contrast to the base color in order to not remove
contrast to the text.
On Android this enables the application to run just a simple
quick sync and then exit the app on regular intervals.
The main benefit is that when the user doesn't run the app very
often they will avoid having a long sync time.
Add logic to notice that the device is offline and notify the
user of this fact on screen.
Repeat checking so we can notify the user that network is back.
This shows in the UI (of the mobile form factor) that the device
is offline and we avoid starting the p2p layer until network
is detected to be there again.
We should not require the user to put it in a layout with spacing, that
will just create inconsistencies.
Instead make sure that the button itself is tall enough for easy aiming
on small screens.
This adds a lock to ensure that the app is not started twice, which
would be bad for data consistency.
The second version will just show a simple window stating it is already
running. While it would be nice to make it more advanced, I don't think
that is useful to spent time and code on.
tomFlowee