The flex security sandbox ensures the security, and at the same time, it hurts many people like me.

To create a SWF, you can run it locally (instead of uploading it to the server as a website) and load XML

File and run executableProgram.

As a result, the flex security sandbox quickly abolished me.

After a long time, I finally solved the problem.

There are two main problems:

The first problem is running local files with SWF. In general, this is naturally not the case. Let's take a look at what will happen in the world if SWF can run EXE and other programs without restrictions?

However, some settings can still be run.
Core of running EXE in flexCodeYes:
Fscommand ("EXEC", "xxxx.exe ");

Next:
Create a folder in the resource folder namedFscommand
Put the program you want to execute in it. Double-click the normal SWF, and click File> Create broadcast after running.

Put, enter the file name, just enter one.

In this way, SwF will be encapsulated in the player for execution, and the files to be executed will also be placed in a fixed folder,

The Security Sandbox will generally not bother you.

It should be noted that clicking debug directly does not work. You need to click the SWF file to make it take effect.

.

 

Second question:
SWF files cannot call local XML files. When using relative paths, it is okay to put them on the server.

However, if you change the project folder locally, an error is reported. Or permission issues.
Solution: Right-click the project and selectProperties --> flex compiler --> additional compiler arguments
Add "-use-network = false"In this way, no matter where you move the entire project folder, It will be executed in the relative path.

Hope to help everyone ^_^

 

The space of green tea at 66 ℃ is original. Please indicate the source for reprint. Thank you.