[Flashcoders] Understanding dynamic classes

2006-02-01 Thread Helmut Granda
Since we are in the understanding mode, I want to throw a question out there. Las week I made a component similar to the radio button component. While I was working on this I requested help understanding the way the component works. Eric (ericCD) suggested making a manager class: -- Make

Re: [Flashcoders] Understanding dynamic classes

2006-02-01 Thread Troy Rollins
On Feb 1, 2006, at 7:00 PM, Helmut Granda wrote: Las week I made a component similar to the radio button component. While I was working on this I requested help understanding the way the component works. Eric (ericCD) suggested making a manager class: In a general sense, the concept is

Re: [Flashcoders] Understanding dynamic classes

2006-02-01 Thread Helmut Granda
Troy, thanks for such a great explanation. I had the same idea I just cant wrap it around my head in programming termns. For example if I have a property (array) inside a class it must be public so other intances of the object I create can access that property and they can write to it? And if

RE: [Flashcoders] Understanding dynamic classes

2006-02-01 Thread Bjorn Schultheiss
: Thursday, 2 February 2006 2:14 PM To: Flashcoders mailing list Subject: Re: [Flashcoders] Understanding dynamic classes Troy, thanks for such a great explanation. I had the same idea I just cant wrap it around my head in programming termns. For example if I have a property (array) inside a class

Re: [Flashcoders] Understanding dynamic classes

2006-02-01 Thread Troy Rollins
On Feb 1, 2006, at 10:23 PM, Bjorn Schultheiss wrote: Has anyone come across an essential use for a Dynamic Class while developing an RIA, besides laziness. Not if you go and rule out the number one reason I've done it just like that. ;-) -- Troy RPSystems, Ltd.

Re: [Flashcoders] Understanding dynamic classes

2006-02-01 Thread Troy Rollins
On Feb 1, 2006, at 10:14 PM, Helmut Granda wrote: For example if I have a property (array) inside a class it must be public so other intances of the object I create can access that property and they can write to it? And if that is true, how would I avoid having the property re-assigned

Re: [Flashcoders] Understanding dynamic classes

2006-02-01 Thread Helmut Granda
Troy, Lots of great advise, I felt for a minute I had it but then all of the sudden everything faded away... Where I get confused is when I have to pass the reference from the button to the manager function. All the methods come from the same class? for a minute I thought I needed 2 classes

Re: [Flashcoders] Understanding dynamic classes

2006-02-01 Thread Troy Rollins
On Feb 2, 2006, at 12:24 AM, Helmut Granda wrote: Where I get confused is when I have to pass the reference from the button to the manager function. All the methods come from the same class? for a minute I thought I needed 2 classes (1 to initiate the button, 2 to handle the references of