On Wed, Sep 2, 2009 at 2:59 PM, Rick McGuire<object.r...@gmail.com> wrote:
> Well, I'll answer the question you're actually asking, but then I'll
> give you a better option.
>
> One of the new additions to 4.0 was a sendWith() method, so you can use
>
> .FileNameDialog~sendWith("GET", arg(1, 'A'))
>
> will give ou what you want.
>
> However, there's another option. I suspect many of the untility
> routines you've written actually require a RexxThreadContext rather
> than a RexxMethodContext. Both the method context and the call
> context have an embedded thread context pointer. If your utility
> toutines don't require any of the methods that are unique to a method
> context, then you can pass the RexxThreadContext pointer instead to
> have common routines.
Aha. Great for both answers.
I should have known the second answer because I had asked a question
about why you used the RexxThreadContext pointer in some of the OLE
native functions before. It was for a different reason, but should
have been enough to give me a hint if I had been thinking.
--
Mark Miesfeld
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
