Flash Player 10 and IDE CS4 problems

Question

Well, first I installed the new flash CS4 to test and made a
simple webpage with no code. I added a button and a Motion tween
animation that makes a box to go from a point to another. 35 frames
total, and a 'stop():' at the end of the timeline. The stop(); is
the only code.
Then I publish and test on the browser IE7, and I also open
the Task Manager. Ok, and the problem is: even with the animation
stoped at the frame 35, IE7 with the flash running is eating 4k of
memory from time(seconds) to time. 4k only for just one motion
tween that go increasing over time is not good. But if I remove the
layer with the motion tween, the 4k memory usage increasing stops.
Another problem is: if I add a component button on the a
scene, it works ok. But if I add another scene, add one instance of
the button component, and try to edit its label parameter, it will
give an error message when I run the movie. This one:
TypeError: Error #1009: It is not possible to access a
property or method of a reference of a null object.
at
testeCS4_fla::MainTimeline/__setProp___id1__Scene2_Layer1_0()
at testeCS4_fla::MainTimeline/frame1()
But the only thing that I change is its label text, using the
component inspector parameteres panel.
One more:
The script generated by Flash IDE when we publish to a
webpage, to detect the flash player version is not detecting flash
player 10, even if we have it already installed. Because it only
search for: ("ShockwaveFlash.ShockwaveFlash.7"); and it should be
testing also for ("ShockwaveFlash.ShockwaveFlash.10");

Answer 1

quote:
Originally posted by:
BWolfe [ADOBE]
alexmbra... i'm out of bandwidth to look at this just now.
Make sure the agent working the detection case knows about this
thread, and don't hesitate to ask them to escalate to a senior
agent. We'll get it figured out.
(And to answer your question, all I did was publish from
CS4.. you can look at my detection code source on my site. )
To try to help you out, I put a bunch of alerts inside of the
javascript on this page:
http://www.bentimagemedia.com/escalations/fptendetection/flashplayerversion10.html
That should give us a better idea of what the code is doing
when you view it.
I'm also wondering if perhaps this might not be a language
problem of some kind. If you have some friends who have the same
language OS that would let you test on their machine perhaps we'd
see similar results?
Ok. I have 3 computers at my home where I was testing this,
and I was getting the same problem and I had installed flash player
version 10,0,12,36 at the same time os all 3 computers.
But I found the problem. When we install flash player 10, it
will add a new key inside the registry saying this:
"ShockwaveFlash.ShockwaveFlash.10", and it will also change
the value of the
"ShockwaveFlash.ShockwaveFlash/CurVer" key to:
"ShockwaveFlash.ShockwaveFlash.10" also.
But looking at my registry ( you can see here also:
http://server6.theimagehosting.com/image.php?img=flashProblem.jpg&album=0&fullsize=1
), after installing the flash player 10, the value of "CurVer" was
still saying "ShockwaveFlash.ShockwaveFlash.9" for some reason. So,
I guess it was a installation failure that happened at the same
time on all the 3 computers that I use.
So, the problem is now fixed because I unistalled flash from
all computers and installed it again. Now the registry is right
("ShockwaveFlash.ShockwaveFlash/CurVer" key has:
"ShockwaveFlash.ShockwaveFlash.10" ), and the detection code is
working and showing the right version.
So, the problem is fixed, but 2 questions remains:
1- How did flash player failed to right the right value when
installing?
2- How the Adobe FlashPlayer instalation version ( at Adobe's
) was detecting the right version insalled and all other codes were
not?
Anyway, thanks for you help.
Now, there is that very important problem of flash motion
tween eating memory.