--
Project repos: github.com/projectmesa
---
You received this message because you are subscribed to the Google Groups "ProjectMesa" group.
To unsubscribe from this group and stop receiving emails from it, send an email to projectmesa...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/projectmesa/5e856b44-1caa-4b90-9358-8784523b6629n%40googlegroups.com.
There is just one catch. Right now each connection *kind of* shares the same model. Some things will be the same, some will be very different. It's really very confusing.
But this PR should solve that: https://github.com/projectmesa/mesa/pull/934It's a bit more involved to use a custom build on heroku based on this PR, but maybe we can push it into the next release of mesa. When is your course going to happen?
I am also currently thinking about how to further improve the visualization server so that model state logic is kept cleanly separated from the server itself. This could make it possible to have a custom front page before the actual model, which could be interesting for you. Would love to hear more about your use case (how you would like it to be)
Ah! So if an entire class was playing around synchronously, there could be some odd and unexpected behavior?
--
Project repos: github.com/projectmesa
---
You received this message because you are subscribed to the Google Groups "ProjectMesa" group.
To unsubscribe from this group and stop receiving emails from it, send an email to projectmesa...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/projectmesa/cc10187e-191d-4989-98a6-af2ba660cdd1n%40googlegroups.com.