|
Well, all Flex developers use containers
very early in their work, and referencing / setting properties on hidden
components is a basic task common to most all environments. However, manual
control of instantiation, and even binding, in order to optimize the
performance of an application is fairly advanced stuff. If all they want to do is learn how to
work with components in their first test application, creationPolicy=”all”
can get a newbie coding again. You can hear the frustration folks are
experiencing when they post this question. Saying “No, Flex is not
broken, and you are not stupid, try this, and your code will work”, is sometimes
ok. Recreational use of creationPolicy=”all”
should not be illegal. It is just a matter of education. From: On
10/30/06, Gordon Smith <[EMAIL PROTECTED] -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___ |
- RE: [flexcoders] JUST SAY NO to creationPolicy="all&qu... Alex Uhlmann
- RE: [flexcoders] JUST SAY NO to creationPolicy="a... Benoit Hediard
- RE: [flexcoders] JUST SAY NO to creationPolicy="a... Tracy Spratt
- Re: [flexcoders] JUST SAY NO to creationPolicy="a... greg h
- RE: [flexcoders] JUST SAY NO to creationPolicy="a... Gordon Smith
- Re: [flexcoders] JUST SAY NO to creationPolicy="a... Peter Hall

