From a309f237f240902161878d564de30f6a933afc6d Mon Sep 17 00:00:00 2001
From: Robin Gareus <robin@gareus.org>
Date: Wed, 9 Feb 2022 21:09:01 +0100
Subject: [PATCH] Allow direct trigger -> trigger selection changes

Previously there were two signals for a ::set()
1. Clear Selection -> Emit Signal
2. Select TriggerEntry -> Emit Signal

As result the Trigger Patch Selector was reset and hidden at (1),
only to be set and presented again at (2).

This should perhaps be done for other ::set() calls as well.
---
 gtk2_ardour/selection.cc | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/gtk2_ardour/selection.cc b/gtk2_ardour/selection.cc
index 9638696d69..a32d0c3c12 100644
--- a/gtk2_ardour/selection.cc
+++ b/gtk2_ardour/selection.cc
@@ -1704,8 +1704,20 @@ Selection::selected (TriggerEntry* te) const
 void
 Selection::set (TriggerEntry* te)
 {
+#if 0
 	clear();
-	clear_triggers ();
+#else
+	clear_tracks ();
+	clear_regions ();
+	clear_points ();
+	clear_lines ();
+	clear_time ();
+	clear_playlists ();
+	clear_midi_notes ();
+	clear_markers ();
+	pending_midi_note_selection.clear();
+#endif
+	clear_triggers (te ? false: true); /* Do not emit signal here, add() emits signal */
 	add (te);
 }