From b080429b2fca4f65172384341351d04a8018be6d Mon Sep 17 00:00:00 2001
From: Dominik Nakamura <dnaka91@gmail.com>
Date: Mon, 4 Sep 2023 11:13:36 +0900
Subject: [PATCH] Handle event messages even without `event` feature

An error message was logged when receiving events from obs-websocket,
when the `events` feature was NOT enabled.
---
 src/client/mod.rs | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/src/client/mod.rs b/src/client/mod.rs
index 5ea03b4..df97f96 100644
--- a/src/client/mod.rs
+++ b/src/client/mod.rs
@@ -258,11 +258,18 @@ impl Client {
                             trace!(?event, "got OBS event");
                             events_tx.send(event).ok();
                         }
+                        #[cfg(not(feature = "events"))]
+                        ServerMessage::Event => {
+                            trace!("got OBS event");
+                        }
                         ServerMessage::Identified(identified) => {
                             trace!(?identified, "got identified message");
                             reidentify_receivers2.notify(identified).await;
                         }
-                        _ => return Err(InnerError::UnexpectedMessage(message)),
+                        _ => {
+                            trace!(?message, "got unexpected message");
+                            return Err(InnerError::UnexpectedMessage(message));
+                        }
                     }
 
                     Ok(())