My main FLA file calls in two swfs in two areas of the timeline. SWF1 gets data from an XML file. SWF2 reads a different XML file. I run the main SWF, invoke SWF1, the data looks fine. I go to SWF2, the data is the same data as from SWF1. You who already know the answer, good on you!
I tried unloading the old SWF1. I renamed instance names in SWF2. I renamed variables in SWF2. I thought I was reading the wrong data file. I renamed variables in the XML file. As with all my Flash adventures, I kept butting my head against walls til there was nowhere else to go. I did notice that when I reloaded the main SWF, the problem sort of went away. That’s when I had the glimmer of an idea that it had to do with the cache. Identifying the source of the problem is 9/10’s of the battle.
A google on “preventing xml cache flash” gave me the solution. Thanks to Ziyad at flashden
Four hours worth of wall hammering, and one measly statement cured the problem. It only works when the swf is uploaded to the server, and will break when testing locally.
How do you change the size of a textbox, without the text inside being squished or stretched?
Answer: Click on the box until you get to point of text input (white inner box with handles). Grab the handles then, and not before.
I could use a nap now.
When is an EQUAL not an EQUAL? when it’s a DOUBLE EQUAL. You Flashy people know EXACTLY what I’m talking about, don’t you? Smarty pants.
In programming languages of old, “If A=B” used to mean “if A equals B”. But not in flash, it don’t mean diddly.
the trace shows true
the trace shows false
If A=False, then do stuff.
It failed to do stuff. WHY? Because Flash need the comparison operator EEEEEQUAL. as in If A==False, not the assignment operator =
Aaargh! That one killed me. That’s what happens when you give a programmer just enough knowledge to royally screw things up.