Meter refactoring

[FrancescoCeruti]

I'm not 100% satisfied with the current "DBMeter", this pull address a few points

• since it can actually be used to measure other parameters, we can this more obvious by using a different name
• condense a few arguments that, in some cases are dependent, into a new "Scale" class (min, max and the scale function)
  • we might move the label and steps into this, but allow users to init with theirs values
• Reduce scale label density to avoid collisions at certain screen sizes
• Use more pixmaps to reduce iterations in the paintEvent
• Make the paintEvent code more coincise and reduce the use of magic numbers

Any feedback is welcome :)

[s0600204]

I notice that the bottom edge of the meter isn't drawn - or more that it is, but outside the widget:

---

I was wondering if you've considered making the meter widget available separate from LiSP? Such a thing could be useful for other audio software projects (I have a couple on the go that could make use of it); a quick look on PyPi and here on GitHub didn't turn up any alternatives; and I don't really want to copy-paste parts of LiSP code into my own projects.

[FrancescoCeruti]

Thanks for the feedback :)

I was wondering if you've considered making the meter widget available separate from LiSP? Such a thing could be useful for other audio software projects (I have a couple on the go that could make use of it); a quick look on PyPi and here on GitHub didn't turn up any alternatives; and I don't really want to copy-paste parts of LiSP code into my own projects.

I've not considered it, I'll look into it