1. When fader is dragged faders on other selected tracks will move relatively.
2. When value is changed in gain display (from keyboard) on any of the selected tracks - values on all selected tracks will be updated.
3. When fader on on of the selected tracks is pressed with Alt (set to default), default values will be set on all selected track faders.
[Reviewed by QA] Andrii Mishyn
Fixed two bugs. Not specified in TT.
1.Ranges which coincided with region borders (achieved by the context menu commands like Move Range Start/End ... ) used to cut a small byte of region which border coincided.
2. If you cover region with a range which start coincides with region's start and ends coincides as well when you drag such range it does cut the whole region, but it does not remove it. Process similar to "copy" accures when "cut" operation is expected.
atof() on Windows expects "," (comma) as float delimeter and ignores "." (dot). So on windows atof("0.1") would return 0.
Unlike MAC.
Proposed fix should work on all platforms.
There were several changes made here. The most important one is to avoid unpacking and
repacking meters every time ::setup_meters() is called, because this forces a full
reset of the widget style which is (relatively) expensive. Another is to check
that the IO configuration really has changed before resetting meter configuration. Finally,
a quick hack has been added to subtract two from the apparent length of a FastMeter.
The final hack will be removed and addressed by a more correct and robust solution within
the next 24-36 hours.
For mass/global rec-enables, that generates excessive iterations across the entire route list.
Instead, catch the change after a request to the session to change rec-enable state.
NOTE: there are still at least two methods for a user to bypass the session when rec-enabling
a track. One is via the Track::rec_enable_control(), the other is an OSC command or similar. These
both need to be fixed to go via the session mechanism.
This more or less obsoletes the DisplaySuspender.
While RAII is nice, the DisplaySuspender cannot be
used from outside gtk2_ardour eg Mute/Solo signals
notifications from libardour (which don't originate
from the GUI).
The DisplaySuspender is still useful, because it
explicitly disables re-display and forces a single
expose at the end.
Conflicts:
gtk2_ardour/editor_routes.cc
gtk2_ardour/editor_routes.h
