Closed GoogleCodeExporter closed 9 years ago
This is controlled by the menu param in the publish settings and is not a bug.
Please
post questions in the mailing list (or do a 1 min Google search) before posting
invalid
bugs.
Original comment by aran.rhee@gmail.com
on 11 Oct 2009 at 11:04
Hmm, I think it IS a bug, but not by you but by Adobe... It stayes greyed out,
even if 'Display menu' is checked
Original comment by ap.van.G...@gmail.com
on 4 Nov 2009 at 2:48
Ok, I belive I have tracked down what is causing the issue. There is a minium
size
required on the swf in order for the settings option menu item to be enabled.
The UI for the settings menu needs at least 214px width by 137px height to show.
BTW - this is the exact same dimensions required to show the Express Install
dialog.
The out of the box examples are 300x120px, so the height is stopping the dialog
showing. I will look at updating the example files to adhere to the minimum
dimensions...
Original comment by aran.rhee@gmail.com
on 5 Nov 2009 at 1:53
[deleted comment]
Is this issue fixed? My SWF is full browser size but the settings option is
still greyed out. It doesn't matter if I change displaymenu to true (also, I
don't WANT to display the menu, I only want the settings).
Original comment by erik.kat...@gmail.com
on 28 Mar 2011 at 12:45
This is a limitation of Flash Player and not a SWFObject bug. I've added the
item to the Frequently Asked Questions page:
http://code.google.com/p/swfobject/wiki/faq#25._Why_is_the_"Settings..."_option_
in_the_Flash_Playe
If you feel this requires further investigation, please provide more details,
including a link to a (non)functioning example.
Original comment by platelu...@gmail.com
on 24 May 2011 at 5:20
not sure if this has been answered or not, but having the wmode param set to
gpu will
disable the settings menu.
<param name="wmode" value="opaque" /> = good
<param name="wmode" value="transparent" /> = good
<param name="wmode" value="window" /> = good
<param name="wmode" value="gpu" /> = bad
Original comment by m...@inveroak.com
on 23 Jun 2011 at 1:21
Original issue reported on code.google.com by
pgpatr...@gmail.com
on 8 Oct 2009 at 8:19