[mtasc] Problem Creating a mx.remoting.Service Object

[hank williams]

Its embarassing. I'm old. I cant remember - but if there were any they
were minor.

Hank.

On 9/25/05, JesterXL <jesterxl at jessewarden.com> wrote:
> So, there were no compile errors with the Remoting code when you chagned it
> so MTASC could compile it in, or were there, but they were minor?
>
> ----- Original Message -----
> From: "hank williams" <hank777 at gmail.com>
> To: "MotionTwin ActionScript2 Compiler List" <mtasc at lists.motion-twin.com>
> Sent: Sunday, September 25, 2005 3:18 PM
> Subject: Re: [mtasc] Problem Creating a mx.remoting.Service Object
>
>
> > Hank, I could post the changes needed to get the Remoting components to
> > compile in MTASC, but because of their MX moniker, you'd still have MTASC
> > ignoring them, even if they worked.
> >
>
> Jesse,
>
> The remoting code works fine for me in MTASC.
>
> As I said, I changed all the names to com.remoting.* so that I could
> use them with the -mx flag. The issue is not the code working, its the
> isssue that you need the -mx flag which means MTASC ignores the
> remoting code (which you dont want) while it also ignores the other
> mx.* files (which you do want).
>
> Hank
> --
> MTASC : no more coffee break while compiling
>
>