Add ProgressIndicator control

[promag]

Add and use the ProgressIndicator control. It can be seen as a more light version of the ProgressBar control.

The example captures mouse clicks to update the progress.

[GBKS]

Looks good. Any chance that the progress change is animated? So it would smoothly move from one position to the other, with some easing applied maybe?

[promag]

Yes, something like:

Behavior on progress {
   SmoothedAnimation {
       velocity: 2
   }
}

[promag]

@GBKS added animation.

[GBKS]

I am not able to build this one. Getting a series of libbitcoin_util.a(libbitcoin_util_a-strnlen.o) has no symbols messages. The main branch builds fine, what could be the problem here?

[promag]

Let me rebase this branch @GBKS

[hebasto]

@GBKS

I am not able to build this one. Getting a series of libbitcoin_util.a(libbitcoin_util_a-strnlen.o) has no symbols messages.

These messages must be completely harmless.

[GBKS]

Thanks for looking into this. Here's more of the error message. Does not seem harmless, but I might not be interpreting this correctly.

make[3]: *** No rule to make target `libunivalue.la'.  Stop.
make[2]: *** [univalue/libunivalue.la] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

[promag]

Rebased.

[hebasto]

@GBKS

Thanks for looking into this. Here's more of the error message. Does not seem harmless, but I might not be interpreting this correctly.

make[3]: *** No rule to make target `libunivalue.la'.  Stop.
make[2]: *** [univalue/libunivalue.la] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

What are your ./configure srcript options?

[hebasto]

Tested 83c21f6 on Linux Mint 20.2 (Qt 5.12.8), and it looks great!

@promag

Is it your intention to get the demo commit merged?

[hebasto]

Could we avoid magic numbers?

[promag]

We need to move these constants somewhere, something to follow up.

[promag]

Is it your intention to get the demo commit merged?

@hebasto yes I think it's fine. What would be the alternative? Drop the commit before merging? Or we should have a separate branch with these demos?

[hebasto]

ACK 83c21f6

[GBKS]

ACK 7dc95a0. A small change would be to speed up the transition a little by setting velocity to 1.5.

Overall I'd prefer a consistent animation duration (200ms or so) for this component with a cubic-bezier(0.5, 0.0, 0.2, 1) easing curve, but we can tweak that some other time, not sure if QML is set up for that easily.

[promag]

@GBKS changed animation as suggested.

[Bosch-0]

Progress bar on Windows 10 is not full even though the network is up to sync.

[GBKS]

ACK 1bf3d5d. Thanks for the animation tweaks.

@Bosch-0 I think the bar is just meant as a sample UI element, and not to reflect the sync status.

[Bosch-0]

ACK 1bf3d5d

Okay sweet, wasn't sure :)