summaryrefslogtreecommitdiff
path: root/libs/surfaces/faderport
diff options
context:
space:
mode:
authorRobin Gareus <robin@gareus.org>2019-04-01 22:30:16 +0200
committerRobin Gareus <robin@gareus.org>2019-04-01 22:30:16 +0200
commit6d335be41835ebd7ed3e0846c235623b79e055ba (patch)
treee67afe1d774dd0cdf11252b6203cf1cdb72ba502 /libs/surfaces/faderport
parent50e8c4d5298e4786f7a4c751ad6fbf87ef8e8da2 (diff)
Indicate automation-latch as "touch" on the FP1
The FP1 does not have a dedicated "Latch" control, but this does at least consistently indicate that Touch, rather than show some arbitrary LED state.
Diffstat (limited to 'libs/surfaces/faderport')
-rw-r--r--libs/surfaces/faderport/faderport.cc1
1 files changed, 1 insertions, 0 deletions
diff --git a/libs/surfaces/faderport/faderport.cc b/libs/surfaces/faderport/faderport.cc
index ed2393e0e2..da2792dbd5 100644
--- a/libs/surfaces/faderport/faderport.cc
+++ b/libs/surfaces/faderport/faderport.cc
@@ -1199,6 +1199,7 @@ FaderPort::map_auto ()
get_button (FP_Touch).set_led_state (_output_port, false);
break;
case ARDOUR::Touch:
+ case ARDOUR::Latch: // XXX
get_button (FP_Read).set_led_state (_output_port, false);
get_button (FP_Write).set_led_state (_output_port, false);
get_button (FP_Touch).set_led_state (_output_port, true);