Add progress bar

[fwsmit]

This PR addresses #772. It add a progress bar at the bottom of the notification when a value is passed via a dbus hint. Settings have been added to turn off the progress bar. The old behaviour of showing a percentage in text can still be used the same way and even in conjunction with the progress bar.
A highlight colour is added and used for drawing the progress bar.

• Bug: Icons larger than max_icon_size don't get drawn
• Add more configuration variables
• Make sure the border is pixel-aligned to avoid anti-aliassing
• Let the progress bar define the width of the notification as well
• Add tests
• Documentation

This is what it currently looks like

Example usage

notify-send -h int:value:10 "Brightness" 

[codecov-io]

Codecov Report

Merging #775 (4f10496) into master (93b52df) will decrease coverage by 0.41%.
The diff coverage is 25.71%.

@@            Coverage Diff             @@
##           master     #775      +/-   ##
==========================================
- Coverage   65.94%   65.53%   -0.42%     
==========================================
  Files          29       29              
  Lines        5162     5225      +63     
==========================================
+ Hits         3404     3424      +20     
- Misses       1758     1801      +43     

Flag	Coverage Δ
unittests	65.53% <25.71%> (-0.42%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/draw.c	0.00% <0.00%> (ø)
src/rules.c	49.25% <33.33%> (-0.75%)	⬇️
src/notification.c	64.55% <75.00%> (+0.12%)	⬆️
src/settings.c	59.29% <77.77%> (+1.24%)	⬆️
test/dbus.c	99.11% <0.00%> (+0.44%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 93b52df...4f10496. Read the comment docs.

[tsipinakis]

Some code style nitpicks and you also forgot to add the new settings to the example dunstrc.

This PR was a breeze to review and couldn't even find any breaking bugs. Huge kudos! :)

[fwsmit]

Thank you for the review. I have addressed everything. The tests are failing, because progress values greater than 100 are being changed to 100. Is there a reason why it's better not to change them to 100?

[tsipinakis]

Is there a reason why it's better not to change them to 100?

There can be cases where the progress can be >100%, think for example volume levels with pulseaudio that can go to 150+. So it's best to handle it here so %p is still accurate.

[fwsmit]

Good point. I have applied your suggestion

[tsipinakis]

You can set this to true as well, the goal is to have this and dunstrc in sync at some point not make it diverge more :)

[fwsmit]

Oh I forgot that one. I changed it now

[tsipinakis]

Merged! Thanks for your work.