Have you tried setting creationPolicy ?.
Just say creationPolicy="all"
--Suresh Akula
--- Robert Brueckmann
<[EMAIL PROTECTED]> wrote:
> I'll play with the config file and let you know what
> I find...thanks
> again for the help! Gotta love these things that
> you spend days on with
> no obvious cause...grrr! Thanks again!
>
> Cheers,
>
> robert l. brueckmann
> vice president
> merlin securities
> 595 madison avenue
> new york, ny 10022
> p: 212.822.4821
> f: 212.822.4820
>
> -----Original Message-----
> From: [email protected]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Simon Fifield
> Sent: Tuesday, April 25, 2006 1:52 PM
> To: [email protected]
> Subject: RE: [flexcoders] Re: Flex 1.5 - Cairngorm
> .99 - Binding VO to
> TextInput help please
>
> Hi Robert,
>
> Although on the surface of things our problems were
> not the same, I'll
> bet
> it's the same thing somewhere under the hood of the
> Flex 1.5 compiler
> that
> is causing these "strange" binding problems to
> occur.
>
> I keep reading of more and more people that are
> encountering this
> binding/compilation bug.
>
> Have you tried changing your flex-config.xml
> settings to not keep the
> compiled mxml components:
>
> <!-- cache compiled custom components as swo
> files -->
> <cache-swos>false</cache-swos>
>
> And maybe try some of the other cache/compiling
> settings to see if this
> resolves your problem. Compiling may be a little
> slower but it may be a
> better workaround than you currently have.
>
>
> With the growing number of people having these
> "mysterious" problems I
> wonder if Adobe are going to release an update to
> resolve them.
>
>
> Regards,
> Simon
>
>
>
> -----Original Message-----
> From: [email protected]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Robert Brueckmann
> Sent: 25 April 2006 18:19
> To: [email protected]
> Subject: RE: [flexcoders] Re: Flex 1.5 - Cairngorm
> .99 - Binding VO to
> TextInput help please
>
> Thanks for taking the time for the detailed reply
> Simon! I WISH it was
> validator related. In one instance, I am using a
> validator but the
> first
> time I saw this behavior was in a simple MXML file
> that had 3 lists that
> get
> populated with 3 separate message types and directly
> next to the lists
> is a
> title label and a text area...when the user clicks
> on a message in any
> of
> the 3 lists, the title and text area should be
> updated with the selected
> message's title and body content.
>
> The title label and body text area have their text
> attributes bound to
> {ModelLocator.selectedMessage.title} and
> {ModelLocator.selectedMessage.body}
> respectively and the change listener on all 3 of the
> lists is simple
> ModelLocator.selectedMessage =
> event.target.selectedItem;
>
> This NEVER works upon first compilation after a
> fresh server restart.
> If I 'touch' the file that contains this message
> reader component and
> refresh my browser...magically, the title and body
> start appearing when
> I
> select a message in the lists.
>
> This behavior escapes me and is obviously not
> conducive to a production
> release because I can't exactly go in and 'touch'
> all necessary files
> for
> this behavior to be fixed...this should work the
> first time.
>
> I even have a test button on the message reader page
> that, upon first
> time
> server start and app compilation, when I click on a
> message and the
> ModelLocator.selectedMessage object have been set
> but the title and body
> do
> not appear, I can click on this button and in an
> alert body display the
> title and the body of the selectedMessage object...I
> am confirming the
> selectedMessage object is getting set with the
> proper information, the
> damn
> TextInput components do not want to show it to me
> though...if I open up
> FlexBuilder, open up my MessagerReader.mxml file,
> hit the spacebar,
> backspace and then save it, refresh my
> browser...magically it all works
> properly. It's that initial load that is completely
> baffling me.
>
> I've tried debugging and because my components are
> being created as
> children
> on the fly it doesn't see the breakpoints I'm
> setting up. I'm at a
> loss.
>
> My work around, and this is the kicker, if I take
> the two fields that
> currently, in the same component, reside next to the
> 3 lists, and wrap
> them
> up into their own MXML file component and add a
> COMPLETELY EMPTY
>
> public function set message(m:Message){}
>
> method call in this new wrapped up component and
> then in the original
> message reader component, do this:
>
> <comp:MessageReaderFields width="100%" height="100%"
> message="{ModelLocator.selectedMessage}" />
>
> And now, when I select a message, first compilation,
> 14th compilation,
> 1st
> server restart, 10th server restart, the message
> title and body field
> binding to the ModelLocator.selectedMessage object
> in my new embedded
> component work as they should. Makes sense, right?
> Nope. Not even a
> little bit.
>
> Whatever...looks like I have a work-around for the
> time being...
>
> robert l. brueckmann
> vice president
> merlin securities
> 595 madison avenue
> new york, ny 10022
> p: 212.822.4821
> f: 212.822.4820
>
> -----Original Message-----
> From: [email protected]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Simon Fifield
> Sent: Tuesday, April 25, 2006 11:33 AM
> To: [email protected]
> Subject: RE: [flexcoders] Re: Flex 1.5 - Cairngorm
> .99 - Binding VO to
> TextInput help please
>
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
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
| Web site design development | Computer software development | Software design and development |
| Macromedia flex | Software development best practice |
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
