rly decisions
were good ones with forethought, so I havent' run into that problem too
much.
Naw, thanks again for letting me know,
I had no clue that property existed.
- Original Message -
From: Jason Hawryluk
To: flexcoders@yahoogroups.com
Sent: Wednesday,
too
much.
Naw, thanks again for letting me know, I
had no clue that property existed.
- Original Message -
From: Jason Hawryluk
To: flexcoders@yahoogroups.com
Sent: Wednesday, July 12, 2006 3:02 AM
Subject: RE: [flexcoders] viewstack design pattern issue
I didn't hear about it,
I jus
er reading your
post.
Jason
-Message
d'origine- De :
flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED]De la part
de JesterXLEnvoyé : mercredi 12 juillet 2006
02:02À : flexcoders@yahoogroups.comObjet : Re:
[flexcoders] viewstack design pattern issue
3 things.Firs
ch all to use. :: shrugs :: Where did you hear about?
- Original Message -
From: "Jason Hawryluk" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, July 11, 2006 6:03 PM
Subject: RE: [flexcoders] viewstack design pattern issue
I don't quite understand how that could be less co
ailto:[EMAIL PROTECTED] la
part de JesterXL
Envoyé : mardi 11 juillet 2006 18:25
À : flexcoders@yahoogroups.com
Objet : Re: [flexcoders] viewstack design pattern issue
:: shrugs :: Never used valueCommitted. Using change for a TextInput for
example causes problems because sometimes updating eve
uillet 2006
15:46À : flexcoders@yahoogroups.comObjet : Re:
[flexcoders] viewstack design pattern issue
We use a dirty flag. We set it to true
whenever some data changes. This data change is detected by registering
for control events that change data (focusOut for TextInput, selectedDa
Hank:
Are you opening the same data multiple times, and you require that
related screens are observed ? I.e. update one, the other updates kind of
thing?
JasonNo, none of that. Actually just think of it like a television, where each of the screens is a different camera angle. So when you
flexcoders] viewstack design pattern issue
We use a dirty flag. We set it to true
whenever some data changes. This data change is detected by registering
for control events that change data (focusOut for TextInput, selectedDate !=
null for DateChooser, etc.). These events change t
hmm... not quite the question I was asking.I presume there would be a dirty flag. My question is about the screens in the viewstack. I am trying to come up with a clean repeatable model for how a screen knows it should recall the server to grab more data.
As an example, consider that all the scr
We use a dirty flag. We set it to true
whenever some data changes. This data change is detected by registering
for control events that change data (focusOut for TextInput, selectedDate !=
null for DateChooser, etc.). These events change the data if applicable,
and set the dirty flag.
10 matches
Mail list logo
