I asume you're using MTASC. There was a flag (I never used it) to workaround
this problem, I think.
Checkout the -mx option: http://www.mtasc.org/
Hope it helps.
Cheers
Juan Pablo Califano
2010/1/13 Andrew Sinning and...@learningware.com
I started looking into using FlashDevelop's code
That seems to compile, but what does it actually do? It says that using
this will cause all the classes from the -mx name space to be omitted
from the swf. How would I get those classes into the swf?
Juan Pablo Califano wrote:
I asume you're using MTASC. There was a flag (I never used it)
hi list,
i'm having absolutely no luck targeting the handle of a seekbar used with an
FLVPlayback component. i only want to read its x value to add a tooltip, which
i've seen on other sites. i have tried using both a skin with a seekbar built
in and ignoring a skin and manually adding a
There is a property for it, I read the source myself.
___
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
I'm using AS2. Does anybody know how to get FlashDevelop to compile a
swf that will trace out to Vizzy Flash Tracer?
I had to set the compile option Use MX classes to true in order to get
my classes to compile, so maybe this is preventing the MX mode to work.
I'm able to get it to trace out
thanks Henrik, care to shed some light on that, i have been through the docs,
googled lots, opened the components and skins to look for it. but whether i try
SeekBarHandle, seekBarHandle, SeekBarHandle_mc, handle_mc, (and other
variations i have found listed) all appended to myFLVPlayback or
I have never used the FLV component, but I suppose you have to import it
first, or nothing will work. (it happens often to me).
___
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Adobe's documentation on this is not crystal clear (to me anyway). Hoping that
someone who's been down this road can point me in the right direction.
My app is hosted on a shared host (webFaction). The swfs are loaded over http.
The users credit card data is transmitted over https. All works
1. Given the server configuration, how can I get around the security sandbox
error when I make a https call?
Load the SWF itself through HTTPS.
2. How bad (or not) is the resulting security created by the
allow-access-from domain=*/
Well, it allows any Flash program to request public URLs
Hi,
I would suggest a workaround is to serve the swf from a secure url
too - that would reassure browsers that their details are secure - not
many people will check the status bar, they tend to look for the padlock
or the address bar - if that's got an https in, then they will be happy,
i have no problem with getting an in instance of FLVPlayback to work, its
playing stopping and scrubbing with a skin. i just can't seem to access the
actual handle in the skin.
the search goes on...
From: pedrok...@gmail.com
Date: Wed, 13 Jan 2010 18:13:06 +0100
Subject: Re: [Flashcoders]
I think that getting a swf running in the browser to connect to
FlashDevelop requires some extra sandbox permissions voodoo.
I solved the problem by putting a function in my source fla that gets
compiled in the IDE into the input swf file:
function traceOut(str:String) {
trace(str);
}
I wouldn't worry about point 2).
The only real reason for crossdomains (as I understand, at least) is solving
this potential security hole:
Let's suppose you're in a LAN that has access to some intranet; or to some
servers that you have access to because you're in this LAN, but are not
Okay I've gotten the server folks to allow me to serve my own crossdomain.xml
file. How do I craft a crossdomain policy file that will allow the swf (served
via http) to access data served via https within the same domain?
Here's my error:
2048: Security sandbox violation:
Hi,
I think you need to add in the secure=false and make sure that is
the cross domain file served from the https connection on the server..
http://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html#allow-access-from-secure
e.g.
allow-access-from
15 matches
Mail list logo
