to answer my own questions > > 1) will i still have to do it that way?
i found a link to Peter Ents flex2 panel. i like the way he's done it. http://weblogs.macromedia.com/pent/archives/2006/03/component_templ.c fm > 2) the "btnAddress.move(100, 100);" doesnt work. any ideas? (my x, y > are hardcoded for this example). the move() does work if i make the <mx:Panel layout="absolute"> > 3) I prefered the flex 1.5 way of having an 'initObj ' (in > createClassObject()) because this object also accepted style > properties. so i wouldn't have to keep calling setStyle(). if we are going to be using the 'new' word to create a uicomponent (eg button), then we'll have to use setStyle() for every style property we want to change. doesn't that just become very memory intensive? -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
