If I haven't bored you yet, I would love to tell you
exactly what the issue is. For a long time now we've
occasionally seen very strange behavior. As I
described before, you'll write something, get
everything working perfectly, then do a clean build
before deploying and suddenly something disappe
---
From: "G" <[EMAIL PROTECTED]>
To:
Sent: Thursday, July 27, 2006 5:22 PM
Subject: Re: initialize vs. construct/init...Re: [flexcoders]
constructObject2() vs. init()? (Flex 1.5)
The code is too complicated to summarize--there are so
many interconnections it would take you da
ginal Message -
> From: "G" <[EMAIL PROTECTED]>
> To:
> Sent: Thursday, July 27, 2006 3:51 PM
> Subject: initialize vs. construct/init...Re:
> [flexcoders] constructObject2()
> vs. init()? (Flex 1.5)
>
>
> > However, you're better off jus
Of course I'm not sure. What are you initializing, and who is expecting
them to be initialized?
- Original Message -
From: "G" <[EMAIL PROTECTED]>
To:
Sent: Thursday, July 27, 2006 3:51 PM
Subject: initialize vs. construct/init...Re: [flexcoders] constructObject2
> However, you're better off just have your initialize
> event call a function
> in your MXML and do non-GUI related stuff there.
Are you sure about that? That seems to be exactly the
source of our problems. If we initialize values in
the initialize handler, it seems they are being
initialized
5 matches
Mail list logo
