You're right. I'm wrong. Sajid is doing something else incorrectly.
___
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
rs window?
What does ClassB look like?
regards,
Muzak
- Original Message -
From: "Sajid Saiyed"
To: "Flash Coders List"
Sent: Wednesday, September 02, 2009 4:07 AM
Subject: Re: [Flashcoders] Problem understanding Class heirarchy issue
Hi,
Thanks all of you for ad
I'm sorry, Steven, that's just not true. Test out the following code:
package
{
public class A
{
public function A()
{
trace("A Constructor");
}
}
}
package
{
public class B extends A
{
ject ClassA]
>> - disptaching MOVE_UP event on 'a'
>> ClassA ::: moveUpHandler
>> ClassD ::: CONSTRUCTOR
>> ClassC ::: CONSTRUCTOR
>> ClassB ::: CONSTRUCTOR
>> - instance 'b': [object ClassB]
>>
>>
>> Exactly a
> ClassC ::: CONSTRUCTOR
> ClassB ::: CONSTRUCTOR
> - instance 'b': [object ClassB]
>
>
> Exactly as expected. From what I can tell, it doesn't really matter which
> class extends which.
> The only thing that matters is that the MOVE_UP event handler
> (
dispatch a
MOVE_UP event on 'a' in the fla.
regards,
Muzak
----- Original Message -----
From: "Sajid Saiyed"
To: "Flash Coders List"
Sent: Tuesday, September 01, 2009 8:12 AM
Subject: Re: [Flashcoders] Problem understanding Class heirarchy issue
Ok, Here is a b
ng invoked.
When is the moveUP event dispatched?
regards,
Muzak
- Original Message -
From: "Sajid Saiyed"
To: "Flash Coders List"
Sent: Tuesday, September 01, 2009 8:12 AM
Subject: Re: [Flashcoders] Problem understanding Class heirarchy issue
Ok, Here is a bit mo
st"
Sent: Wednesday, September 02, 2009 12:56 AM
Subject: Re: [Flashcoders] Problem understanding Class heirarchy issue
In AS2, super() was called automatically (so to speak), so calling it was a
matter of proper form more than anything else. In AS3, you have
In AS2, super() was called automatically (so to speak), so calling it was a
matter of proper form more than anything else. In AS3, you have to call it
yourself or it doesn't get called.
___
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
ht
:
> > addEventListener(ClassC.moveUP, Delegate.create(this, someFunction);
> > to get someFunciton to run in the scope that you expect.
> >
> > --- On Tue, 9/1/09, Steven Sacks wrote:
> >
> >
> > From: Steven Sacks
> > Subject: Re:
; addEventListener(ClassC.moveUP, Delegate.create(this, someFunction);
> to get someFunciton to run in the scope that you expect.
>
> --- On Tue, 9/1/09, Steven Sacks wrote:
>
>
> From: Steven Sacks
> Subject: Re: [Flashcoders] Problem understanding Class heirarchy issue
wrote:
From: Steven Sacks
Subject: Re: [Flashcoders] Problem understanding Class heirarchy issue
To: "Flash Coders List"
Date: Tuesday, September 1, 2009, 9:11 AM
You're not calling super() in the ClassA constructor.
On Aug 31, 2009, at 11:12 PM, Sajid Saiyed wrote:
>
You're not calling super() in the ClassA constructor.
On Aug 31, 2009, at 11:12 PM, Sajid Saiyed wrote:
Ok, Here is a bit more information.
ClassA (works pefrectly fine):
---
package com.folder.subfolder
{
import flash.display.*;
import flash.events.*;
import flash.filters.*;
Ok, Here is a bit more information.
ClassA (works pefrectly fine):
---
package com.folder.subfolder
{
import flash.display.*;
import flash.events.*;
import flash.filters.*;
import flash.utils.Timer;
import com.folder.subfolder.*;
public class ClassA extends ClassC
Are you defining a subclass constructor and then failing to explicitly call
the super() (superclass's constructor)?
On Mon, Aug 31, 2009 at 8:37 AM, Sajid Saiyed wrote:
> I am already importing all the classes in the package.
>
> Still cant seem to get my head around this.
> Maybe later today I
I am already importing all the classes in the package.
Still cant seem to get my head around this.
Maybe later today I will post excerpts of my classes here.
That might help.
Regards
Sajid
On Mon, Aug 31, 2009 at 6:14 PM, Cor wrote:
> Not knowing what you are trying to do, you have to import Cl
When you do ClassA extends ClassC
you should read this as ClassA "is a" ClassC and in him you extend its
functionality
-Original Message-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Sajid Saiyed
Sent: maandag 31 augustus
Not knowing what you are trying to do, you have to import ClassB to
instantiate it in ClassA.
HTH
Cor
-Original Message-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Sajid Saiyed
Sent: maandag 31 augustus 2009 12:06
To: fl
18 matches
Mail list logo
