Process 'default_ui_config.in' when building with MSVC
CLA approved consistent fine-grained scale modifier
update interface for processor-box faders step/page

see also 4d4c20b8c
Save mute automation state.
Factor out duplicated track automation code.

Mute automation for MIDI tracks.
Clean up state tracking of raw MIDI.
Add missing namespace qualifiers.
Move EventRingBuffer to libardour.

This is not used anywhere in Evoral and is just a wrapper around the PBD
RingBuffer anyway.  Towards a (once again?) independently buildable/testable
Evoral and fewer cross-dependencies.
Trim the include tree.
Fix test runner for tests that use files.
Remove bogus test and noisy output.
Remove dead code.
Replace thinning static state with parameter.
Remove braindead Parameter inheritance abuse.
exclude fader-reserve from range
Make tests of Evoral::Range functions include both endpoints in Range

Some of the tests for Evoral::RangeList::subtract() assume that ranges
don't contain their end (->to) point. This appears inconsistent with how
they are used elsewhere.

Add some ASCII art comments to the tests to try to clarify what they're
really testing for, and amend subtractTest1, subtractTest4, & subtractTest5
to incorporate the assumption that ranges include their end points.
Rework Evoral::coverage() to pass unit tests

Rewrite Evoral::coverage() to (hopefully) do what it's supposed to.

Return OverlapNone for invalid ranges: if either of the ranges passed to
Evoral::coverage() have negative length (i.e.  start > end), return OverlapNone
- it seems reasonable to say that a negative-length range can't overlap
anything. Also return OverlapNone from the fallthrough case, though this should
never happen.
Add comment about parameters to coverage() including the end point.
Comments in various call-sites of coverage()

Comments in various call sites of Evoral::coverage() marking things I think
are dubious (with XXX). Also straightened up the alignment of some ASCII
art in libs/ardour/diskstream.cc
Simplify Evoral::RangeList::subtract(), and make it pass amended tests

The various conditionals in Evoral::RangeList::subtract() appear to have
been there to work around
 (a) coverage() not always returning the correct value, &
 (b) the test suite assuming that the ->to point lies outside the range

Now that these are both fixed, the implementation of subtract() becomes
quite a bit clearer. I replaced the if()s with assert()s for now, but these
shouldn't trip if coverage() is working as I expect.

Also (attempt to) clarify the comments in subtract.