Flash Player 10 and IDE CS4 problems

[alexmbra]

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");

[BWolfe [ADOBE]]

Aelxambra, please open support cases for these issues (one case for each issue
would be best).

If you could open a case on the detection issue FIRST I'd appreciate it. Post
back the case number on that one and I'll get an agent on it.

[alexmbra]

Already did it!

Case #0180490603: Detecting flash player 10 error
Case #0180490499: Motion Tween eating memory
Case #0180490602: Button component scenes problem

[BWolfe [ADOBE]]

I posted a couple of detection test pages, published from Flash CS4
Professional Windows:
http://www.bentimagemedia.com/escalations/fptendetection/

There's four pages. Each one detects a lower version number. So there's one
page to detect FP7, one for FP8, one for FP9, and on for FP10.

I don't see any problems hitting these pages with a FP10 browser. What do you
see?

[alexmbra]

[q][i]Originally posted by: [b][b]BWolfe [ADOBE][/b][/b][/i]

[/q]

Well, I went right the way for the

http://www.bentimagemedia.com/escalations/fptendetection/flashplayerversion10.ht
ml, and this is what it returns for me:
[b]Alternate HTML content should be placed here.This content requires the
Adobe Flash Player.Get Flash [/b]

And when I try to install the flash player, it says that I already have it:
"You have version 10,0,12,36 installed", because I already have it installed.

As, I said before: Inside the "function ControlVersion()" on the first
try/catch code block, if I change the "axo = new
ActiveXObject("ShockwaveFlash.ShockwaveFlash.7");" to "axo = new
ActiveXObject("ShockwaveFlash.ShockwaveFlash.10");", it will detect the flash
player 10.

try {
// version will be set for 7.X or greater players
axo = new ActiveXObject("ShockwaveFlash.ShockwaveFlash.7");
version = axo.GetVariable("$version");
} catch (e) {
}

[BWolfe [ADOBE]]

Wierd. They definitely work fine for me and the other folks that have tested
them.

I -suspect- that what's happening is that your machine has ACL permission
issues on the shockwaveFlash registry keys.

Do you get the same detection results in FireFox, chrome or any other non-IE
browser?

[alexmbra]

Yes, I get the same results in FireFox and Chrome.

ACL permission issues? I don't think so. Because the detection always worked
right with other flash player's versions installed. And the Adobe Flash site
detect and it shows the right version 10,0,12,36.

Also, I put this code

alert("version: " + version);

inside the Controlversion function, and it returns this: Win 2,0,0,11.

But if I add one more try to search for "ShockwaveFlash.10", it will return
the right version: Win 10,0,12,36.

Are you sure that you are using the same detection code than mine? Tell, if
only searchs for "ShockwaveFlash.7", how will it ever detect
"ShockwaveFlash.10"?

Also, here is a little screenshot of my registry showing the
"ShockwaveFlash.ShockwaveFlash" keys:

http://server6.theimagehosting.com/image.php?img=flashProblem.jpg&album=0&fullsi
ze=1

[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.ht
ml

That should give us a better idea of what the code is doing when you view it.

[alexmbra]

[q][i]Originally posted by: [b][b]BWolfe [ADOBE][/b][/b][/i]

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?[/q]

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&fullsi
ze=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.

[alexmbra]

[q][i]Originally posted by: [b][b]BWolfe [ADOBE][/b][/b][/i]

I'm also wondering if perhaps this might not be a language problem of some