RE: [flexcoders] JUST SAY NO to creationPolicy="all" !

[Benoit Hediard]

Good question... ;)   We've tried several times to isolate the bugs on more simple app, but without success. Usually, it involves ViewStack, Repeater with RadioButtons and/or Tile. The sizing of mx:Text with a width="100%" can also be very buggy. Very specific and complex cases where the only quick workaround we found was to set creationPolicy to "all". There was perhaps better and more elegant workarounds but as it was working for us, we needed to go on...   Next time I face the problem, I'll try to isolate it. But again, Cairngorm ModelLocator and bindings are the way to go. They can avoid creationPolicy="all" and viewHelpers most of the time.   Benoit Hediard #affinitiz.com De : flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Alex Uhlmann Envoyé : mardi 31 octobre 2006 18:01 À : flexcoders@yahoogroups.com Objet : RE: [flexcoders] JUST SAY NO to creationPolicy="all" ! Hi Benoit,   can you tell us more where bindings didn't work for you?   Best, Alex Alex Uhlmann Consultant (Rich Internet Applications) Adobe Consulting Westpoint, 4 Redheughs Rigg, South Gyle, Edinburgh, EH12 9DQ, UK p: +44 (0) 131 338 6969 m: +44 (0) 7917 428 951 [EMAIL PROTECTED] http://weblogs.macromedia.com/auhlmann   From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Benoit Hediard Sent: 31 October 2006 15:40 To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] JUST SAY NO to creationPolicy="all" ! In most cases and in a "perfect" world, it can be avoided. But in some specific cases, it is very useful, especially to workaround some binding bugs... In our app (a pretty complex one), we use as much as possible the Cairngorm ModelLocator and bindings. But we have some views that could not be configured by bindings or at initialization, so we are using cairngorm ViewHelpers to do that. In order to use viewHelpers, you have to be sure that the view has been instantiated. Deferred instantiation is not "always the way to go". So please, do not remove this option... ;) Benoit Hediard #affinitiz.com -----Message d'origine----- De : [EMAIL PROTECTED]ups.com [mailto:[EMAIL PROTECTED]ups.com] De la part de Adam Dorritie Envoyé : mardi 31 octobre 2006 14:37 À : [EMAIL PROTECTED]ups.com Objet : Re: [flexcoders] JUST SAY NO to creationPolicy="all" ! On 10/30/06, Gordon Smith <[EMAIL PROTECTED]com> wrote: > <rant> > I've never seen a case where it is necessary to push data into the controls before they exist. If you must put the data somewhere in the meantime, store it in data vars, which have none of the startup cost of a visual component, and then move it into the controls after they get created. > > </rant> I guess I'm wondering why, if there is apparently no use case for this "feature" and deferrred instantiation is "the way to go," it is included in the language at all. Is there never a case to use this option? -- 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 __._,_.___ -- 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 Software development tool Software development Software development services Home design software Software development company 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 __,_._,___