RE: inheritance issue...

Thanks ron, it's a mystery alright - if I include a copy of
the 'middle'
class in the inheritance chain in the same package as the
top member of
the chain then all is fine - it works, it's when it's in the
library.swf
that it seems not to get recognized....

By nothing at all I mean absolutely nothing - like it
doesn't trace or
even leave a blank line where a trace might be.... I was
iterating
through the properties of super so it just didn't ever call
a trace() as
there were no iterations carried out.

I've got a workaround (which is actually looking like a
better solution
now anyway) it's a shame to have to do so much work for one
button for
one client but never mind.

Thanks again for the help

T

-----Original Message-----
From: mtasc-bounceslists.motion-twin.com
[mailto:mtasc-bounceslists.motion-twin.com] On Behalf Of Ron
Wheeler
Sent: 22 February 2007 14:37
To: MotionTwin ActionScript2 Compiler List
Subject: Re: [mtasc] inheritance issue...

Tracing the value of 'super' gives [object Object] but
tracing any of 
it's properties gives nothing at all.

What does the property trace look like? "Nothing at
all" is not 
something easy to visualize as a trace output.

On what basis does your Team Leader make the assertion? What
evidence?

Make sure that you are recompiling EVERY swf each time.
See previous discussions on class loading. Class definitions
are only 
loaded once. If an old definition is already loaded from an
swf that you

did not rebuild, then your new definition will be ignored
when it is
seen.

First in Wins

Ron

Trevor Burton wrote:
>
> First of all, thank you very much for mtasc, it's going
to save Sooooo

> much time compiling our applications....
>
> I've spent the last 2 months re-factoring a huge
multiplayer game 
> application to work with mtasc and have an automated
build process and

> I'm on the last leg and have hit a snag...
>
> ...we have a number of 'modules' in the application and
each module
has 
> been broken into a skin, a library, a properties file
and a stylesheet

> - the libraries and properties files being swfs
compiled with mtasc. 
> We have several clients using this application so each
client has a 
> different properties file for each module. Normally the
properties 
> files are just containers of positional values and such
like, they 
> don't contain any functionality - however one does and
is causing an 
> issue with inheritance.
>
> In the library for this module I have an MVC
relationship - the 
> properties for this client's module extend the View for
this 
> relationship - but - when compiled the View doesn't
seem to be able to

> reference it's super class. Tracing the value of
'super' gives [object

> Object] but tracing any of it's properties gives
nothing at all.
>
> The Base Model, View and Controller are in one swf and
the extensions 
> are in another swf, both are loaded at the same time
and not 
> instantiated until both files are loaded so they are
available.
>
> I've tried ditching the extension and instantiating the
super class 
> directly in the child as a test and it works, so the
class is 
> definitely available - but at runtime there's no
extension.
>
> My Team Leader feels it's about multiple inheritance...
I don't - can 
> anyone shed any light on this?
>
> T
>


-- 
MTASC : no more coffee break while compiling

--
MTASC : no more coffee break while compiling