Re: FLASH: FS_Command, Javascript -> Flash [passing variable] GOT IT

[Catherine Kunicki]

hmm. I have a hunch here.  I am working on the same thing right now, and I

have noticed that unless you have your publish settings for Flash with FS

Command, you don't get an <EMBED name=yourmoviename attribute. Try adding

the name attribute and I bet the tutorial will work as advertised.


Reason being I had the same problem for an hour or two (same

window.document.movie has no properties jscript error) , and then I pasted

object and embed code from html that I knew worked and TADA it went. The

only difference was the EMBED name=


After so many many years I would be proud to outguess JD : )


c



----------

>

From: jdowdellmacromedia [dot] com (John Dowdell)

>

To: flasherchinwag [dot] com

>Subject: RE: FLASH: FS_Command, Javascript -> Flash [passing variable]

>Date: Mon, Aug 14, 2000, 6:34 PM

>


> At 2:47 PM 8/14/0, Susan Yoo wrote:

>> I've just been working with the Flash technote mentioned below,

>> specifically with "Using JavaScript methods"... but to no avail.

>

> Hmm, it's hard to troubleshoot this from afar, sorry... the multi-app

> communication could be falling in any of several areas. That's why the

> technotes recommend testing each part of the communication separately,

> starting with simple proof-of-concept and building up to more complex

> examples.

>

> For instance, one recommended test is to see if you can get communication

> in that browser on that machine with known-to-be-good content... the

> "Hawaii" demo is on the CD, and John Croteau has a revised version on his

> site:

> http://www.flashcentral.com/Tech/HawaiiMap/

>

>>From your mention of "window.document.movie has no properties" it sounds

> like you're trying to address the Player, so Netscape browsers would need

> the "swLiveConnect" tag... people also get the same symbol when sending a

> message when the JavaScript loads which is usually before the Player

> loads... could definitely be other causes, though, these are just two

> hunches I have from the warning message.

>

> I'm sorry I can't nail the cause just from the "don't work" symptom alone,

> because this type of troubleshooting requires checking each step... I hope

> the above one-or-all tests, and other troubleshooting techniques described

> in the technotes can quickly identify what's different there, though.

>

> jd

>

> 


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 Full flasher archive now available online at:

 http://www.chinwag.com/flasher/archive.shtml

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

To unsubscribe or change your list settings go to

http://www.chinwag.com/flasher or email

helpchinwag [dot] com