Hello team!
Easymorph parameters aren't mutable but are frozen when a morph project is launched.
However, it's possible to use a parameter via a script function to calculate a value using the context of fixed parameters and values returned by Easymorph functions (which access the system). This isn't very flexible.
In this context, having access to shared memory (on the server or client repository) from script functions would be a really cool feature. It would allow using user-controlled values alongside system values to set parameters more flexibly.
I’d add that this feature could be extremely useful in other areas of parameter management: imagine dynamically populating radio button or dropdown lists via this mechanism! It would enable much greater flexibility. We could write values to shared memory via an earlier morph project and use them dynamically to replace currently static values. So cool!
What do you think?
My use case involves handling default parameters when users don’t know what to enter: they clear the field, and the project calculates the value via a scripted parameter using logic + key/value pairs from shared memory. This could also solve locked parameter issues (server-side).
PS: I get ideas right before falling asleep 
.