change SessionEvent::Immediate to -1, and ensure that clear_events() uses it rather than a hard-coded value

This fixes a design error of using zero as the flag for an "Immediate" event's action frame. Zero
is a perfectly legitimate action frame for an event (e.g. a Skip event), and using zero was causing
skip events with action-frame == 0 to be treated as immediate, not scheduled.

1 files changed, 2 insertions, 2 deletions

diff --git a/libs/ardour/session_events.cc b/libs/ardour/session_events.cc
index 03afd54440..e529c1b94a 100644
--- a/libs/ardour/session_events.cc
+++ b/libs/ardour/session_events.cc
@@ -115,7 +115,7 @@ SessionEventManager::replace_event (SessionEvent::Type type, framepos_t frame, f
 void
 SessionEventManager::clear_events (SessionEvent::Type type)
 {
-	SessionEvent* ev = new SessionEvent (type, SessionEvent::Clear, 0, 0, 0);
+	SessionEvent* ev = new SessionEvent (type, SessionEvent::Clear, SessionEvent::Immediate, 0, 0);
 	queue_event (ev);
 }
 
@@ -168,7 +168,7 @@ SessionEventManager::merge_event (SessionEvent* ev)
 
 	/* try to handle immediate events right here */
 
-	if (ev->action_frame == 0) {
+	if (ev->action_frame == SessionEvent::Immediate) {
 		process_event (ev);
 		return;
 	}