On Thu, May 21, 2009 at 7:36 AM, Rick McGuire <object.r...@gmail.com> wrote: > He wants to use the RexxCallContext pointer to modify the caller's > variables from another thread. This is something that is not > available on an attached thread since you only obtain a thread > context, not a call context.
Thanks Rick. I wasn't of course suggesting that you make any changes to what we have right now. <grin> Just trying to understand things better. So, from a method context or a call context you can get a thread context. Which is the thread the invoked method or call is executing on. >From an interpreter instance you can use AttachThread() to gain a thread context. Now, with that thread context you can use one of the SendMessage() variants to send messages to objects you know about, even if the objects are executing on another interpreter thread. Is that correct? Mostly looking at this from an ooDialog point of view, where I want to send messages from the Windows message loop thread, for a Windows dialog, back to the ooRexx dialog object. The ooRexx dialog is course executing on a different thread than the Windows message loop. As long as I have a good pointer to the ooRexx object, this will work, correct? -- Mark Miesfeld ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
