diff options
author | Paul Davis <paul@linuxaudiosystems.com> | 2016-05-16 11:23:51 -0400 |
---|---|---|
committer | Paul Davis <paul@linuxaudiosystems.com> | 2016-05-31 15:30:42 -0400 |
commit | 8346fab567df898340c2a0f16645256d05aad282 (patch) | |
tree | 8756200b9d98f059725440b4cb0c35496197d87f | |
parent | d5127001bb60a8648a277f77e9ae4e8fd5943c9a (diff) |
remove irrelevant, out of date and incorrect comment
-rw-r--r-- | libs/surfaces/mackie/mackie_control_protocol.h | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/libs/surfaces/mackie/mackie_control_protocol.h b/libs/surfaces/mackie/mackie_control_protocol.h index 37d0b69bb3..8175cda477 100644 --- a/libs/surfaces/mackie/mackie_control_protocol.h +++ b/libs/surfaces/mackie/mackie_control_protocol.h @@ -63,26 +63,6 @@ namespace Mackie { gboolean ipmidi_input_handler (GIOChannel*, GIOCondition condition, void *data); -/** - This handles the plugin duties, and the midi encoding and decoding, - and the signal callbacks, mostly from ARDOUR::Route. - - The model of the control surface is handled by classes in controls.h - - What happens is that each strip on the control surface has - a corresponding route in ControlProtocol::route_table. When - an incoming midi message is signaled, the correct route - is looked up, and the relevant changes made to it. - - For each route currently in route_table, there's a RouteSignal object - which encapsulates the signals that indicate that there are changes - to be sent to the surface. The signals are handled by this class. - - Calls to signal handlers pass a Route object which is used to look - up the relevant Strip in Surface. Then the state is retrieved from - the Route and encoded as the correct midi message. -*/ - struct MackieControlUIRequest : public BaseUI::BaseRequestObject { public: MackieControlUIRequest () {} |