Jefferis,
[quoted text, click to view] > I'm having a problem and not sure it is related, but in
> my Flash, DW's flash publish creates wmode opaque
> in the code.
Does it? Not saying I doubt you, but I'm not sure if you're talking
about Flash buttons built without the mechanism of the Flash IDE. I tend to
create all my Flash content in Flash directly. I certainly use Dreamweaver,
but I don't really use it to create Flash content. Is that what you're
talking about?
[quoted text, click to view] > To prevent this problem, I was using a show/hide
> function to hide my flash item and replace it with a
> jpg when a user scrolled over a menu.
Based on your code sample, it looks like you're using a Project Seven
solution. Project Seven writes terrific code -- they have solid products --
but now there's so much going on, I'm not sure what your problem might be.
It could be Safari's handling of opaque WMODE (have you created a series of
small samples to test?), but then it might be related to your swap-for-a-JPG
approach.
[quoted text, click to view] > For some reason the show hide function is broken,
> probably by the Adobe Scripts update.
Here's another angle. Do you mean the Active Content update? Again,
there's so much going on in this HTML page, it's hard to make a guess. ;)
I would recommend that you break this issue down into small components.
Start a series of fresh new HTML files and embed a small sample SWF in each
one. Make one with no WMODE, make another with opaque, another with
transparent. Set up a small menu that obscures the SWF in each case. Test
in all your browsers. That may be enough to give you the answer you need.
If not, introduce the AC JS code to fix the IE "click to activate" business.
Run your tests again, etc., to give yourself a solid understanding of the
strengths and weaknesses of each scenario.
You may find that you don't need to swap for a JPG -- though that was
good thinking -- and if you don't, hey, the simpler, the better. :) If you
do, then maybe Adobe's Active Content script isn't the best solution. Maybe
you could use Geoff Stearns' SWFObject.
I wish I had a handy answer for you, but in this particular case, I can
only describe the troubleshooting steps I might take. A good portion of
what I know is the result of little private experiments. It takes time to
work that stuff through, but the results are usually worth it. :) Good
luck!
David Stiller
Adobe Community Expert
Dev blog,
http://www.quip.net/blog/ "Luck is the residue of good design."