READ-ONLY SHARED OBJECTSOTHER CONSIDERATIONS
It is important to understand that values returned from the ScriptEase API that follow the usual ScriptEase lifetime rules, such as seobjects, sestrings, and seconstcharptrs, are tied to the context they were created in. Any ScriptEase call that is passed that parameter must be passed the same context used to initially get that item. You cannot use an seobject created in one context with another, for instance.
Fibers are one exception. Fibers are designed to allow several contexts to share the same variables. All fibers in the same fiber group can share these items and use them in any context of the same fiber group. Items created in this way still must not be used with a context that is not part of the fiber group, however.