RE: [Flashcoders] Composition problems

2006-06-16 Thread Merrill, Jason
Given the way you wote the questions class, then: //file: puzzle.as import questions; class Puzzle { private var QA:questions; function Puzzle() { QA = new questions(); trace(QA.qa[0][q]) } } Jason Merrill Bank of America Learning

RE: [Flashcoders] Composition problems

2006-06-16 Thread Merrill, Jason
-Original Message- From: [EMAIL PROTECTED] [mailto:flashcoders- [EMAIL PROTECTED] On Behalf Of Merrill, Jason Sent: Friday, June 16, 2006 4:48 PM To: Flashcoders mailing list Subject: RE: [Flashcoders] Composition problems Given the way you wote the questions class, then: //file

RE: [Flashcoders] Composition problems

2006-06-16 Thread Mendelsohn, Michael
Thanks Jason. I figured it out. I was getting tripped up by the fact that how I was doing it was only returning functions, not properties. In my fixed puzzle class: private function defineQuestions():Void { // create the question and answer data object...

RE: [Flashcoders] Composition problems

2006-06-16 Thread Merrill, Jason
PROTECTED] On Behalf Of Mendelsohn, Michael Sent: Friday, June 16, 2006 4:56 PM To: Flashcoders mailing list Subject: RE: [Flashcoders] Composition problems Thanks Jason. I figured it out. I was getting tripped up by the fact that how I was doing it was only returning functions, not properties

RE: [Flashcoders] Composition problems

2006-06-16 Thread Bernard Visscher
Another things, a lot of people also capitalize class names, but that's personal preference. And if you aren't already, would recommend you organize your classes into packages - will get real messy real quick if you don't. And if you do create packages as Jason proposed.. My personal