From d2b95f21348bf82643794204a32e3742bfacf831 Mon Sep 17 00:00:00 2001
From: Owen Green <gungwho@gmail.com>
Date: Thu, 10 Dec 2020 12:56:34 +0000
Subject: [PATCH] FluidDataObject: Don't send state update and command as
 bundle

Makes reasoning about overall sequences hard if using server latency,
produces 'late' messages otherwise: we just need guarantee of ordering,
not simultaneity.
---
 release-packaging/Classes/FluidServerObject.sc | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/release-packaging/Classes/FluidServerObject.sc b/release-packaging/Classes/FluidServerObject.sc
index eaa8a26..dc23283 100644
--- a/release-packaging/Classes/FluidServerObject.sc
+++ b/release-packaging/Classes/FluidServerObject.sc
@@ -283,12 +283,12 @@ FluidModelObject : FluidDataObject
     }
 
     prSendMsg {|msg|
-        server !? { server.bind(
-            {
-                super.prSendMsg(this.prUpdateStateMsg);
-                super.prSendMsg(msg);
-            });
-        }
+        //These need to happen sequentially, but not simultaneously
+        //sending as a bundle makes reasoning about timing w/r/t other
+        //commands more awkward, unless we set the offet to 0 (in which case,
+        //noisy 'late' messages)
+        super.prSendMsg(this.prUpdateStateMsg);
+        super.prSendMsg(msg);
     }
 }