|
Can I see code that demonstrates this
problem? From: Hi, you seem to be having the same problem
that I had earlier (on popup and binding ) and I faced it again yesterday. I
have an array on my main as file that contains Value objects. I launch a popup window and the popup
window sets it’s internal variable like this iMyArray =
mx.core.Application.application.getArray(); Now this is used in a popup as a
dataprovider for a combobox. Also the popup has a binding on the combobox like
<somevalue>{myCombo.selectedItem.aValueField}</somevalue>. These work nicely until I choose a value,
close the popup and relaunch the popup to edit some data that was setup
earlier. Now the aValueField in the ValueObject that is contained in the array
is undefined (destroyed by flex). ValueObject is otherwise ok, only the field
that was binded on the popup is undefined. I solved this by creating a copy of the
array in the popup and using that (so that it does not reference the array on
the main app -> hence the original array will stay untouched). This way all
works fine, but it’s a real bummer that I have to make a copy of the
array (that is readonly!) so that flex won’t destroy the original
array’s object’s field. I suspect, that the binding & a popup
seems to behave somewhat weird, because it really should not destroy the field
on the object of an array that is defined on the main app when the
popup/binding is destroyed. -Mika From: Is there a limit to a scope of a variable if I store it in
an array because I have done so in the past declared it public at the top of
the mxml file yet at times it seems the computer forgets the value by the time
it goes through like ten functions. Is this unusual and if so is there a way to
prevent this from happening? Yahoo! Groups Links
|
- RE: [flexcoders] applications that forget variables Matt Chotin
- RE: [flexcoders] applications that forget variables Mika Kiljunen
