Something related to :
http://lists.motion-twin.com/pipermail/mtasc/2006-September/029975.html
?
---
Eric Priou
(aka erixtekila)
In progress tech blog : http://blog.v-i-a.net/
Oregano XML Socket forum : http://forum.v-i-a.net/
___
Hi,
not 3 times? I don't think its being called twice in class2, class5's
superclass is class 4, which doesnt not redefine class2's method.
Let class 5 extend class2 for testing purposes, it probably will work
correctly and introduce class3 to see what it does. Then override method1 in
class 3 to
Save the example classes in a folder and look at the output console in
Flash. You will see:
class5 method1
class2 method1
class2 method1
class1 method1
This doesn't have any sense.
If you override the method in class4, or in class3, like this, it works
fine:
code
Class4 extends Class3 {
Hi,
it's discussed here as well, ut i do not know of a fix other than that
described in the post below.
If you dig into the nitty gritty prototype chain information available on
flash you might be able to fix it.
http://chattyfig.figleaf.com/pipermail/flashcoders/2004-January/101029.html
greetz
Sounds like the inheritance chain
Theoretically, seems like when Class 3 4 don't implement the method, the
line of execution goes up the chain until it is: Class 2.
Scott
On 9/28/06, Miguel Angel Sánchez [EMAIL PROTECTED] wrote:
Save the example classes in a folder and look at the
5 matches
Mail list logo
