[ossia-max] Max window spammed with HTTP Error message when deleting model in oscquery-connected patch

[evanmtp]

I have a setup where all of my models are in one patch and my views are in another. The two patches are connected via oscquery. When I delete one of the models, about 90 lines of "HTTP Error: status code 404" get posted to the Max console. It doesn't seem to cause any performance issues or crashes, but it's alarming and clogs up the console a bit.

[jcelerier]

does that still happen ?

[evanmtp]

No, seems to be fine. Here are the patches I used to test just now, if you want to verify: oscquery_test.zip

Steps to test:

1. Open ossia_oscquery_test_client.maxpat and ossia_oscquery_test_server.maxpat .
2. In ossia_oscquery_test_server.maxpat , click the "expose oscquery" message box.
3. In ossia.oscquery_test_client.maxpat, click the "connect oscquery" message box.
4. In ossia_oscquery_test_server.maxpat, delete [p mySynthModel].
5. . Check the Max console for error messages.

Unfortunately, in the course of testing this, I ran afoul of #765 .