|
 |
|
SWF to FLA conversion
Since version 2.0, Flash Decompiler features unique option to convert your SWF files back into FLA.
To do this, select a SWF file and let it be decompiled, so that you see its inner objects (shapes, morphs, images, etc)
in the Resource bar. Now select "Convert SWF to FLA" option on the toolbar.
You will see the export/conversion dialog with two main tabs: "Export SWF objects" and "Convert SWF to FLA". Select the latter.
Here you can customize some conversion settings. Most of them have intuitive and clear labels.
You can also select to open SWF file in Macromedia Flash automatically after it is converted to FLA.
Now select the folder to which you are eager to place the converted FLA file (please, note the "Currently exporting to" field).
When you are ready to convert, press "Export/Convert" button. The activity log will show you the progress and possible errors.
Conversion limitations
When converting a SWF file into FLA you should note several main limitations which are caused by the fact that
SWF format does not have all objects and information which FLA has.
On the other hand, there are many third-party Flash products that generate SWF files which use such features that are only available in
SWF format and cannot be present in the output FLA file. This leads to partial errors while converting a SWF file.
We are working to reduce the number of these errors to the minimum, however, it is not always possible.
We hope that you understand that and will help us reveal more and more weak places in our Conversion process.
You are very welcome to send such erroneously converted files to our Support Team to participate. Here are some of the
situations that can lead to an error:
- If a morph belongs to a clip-layer, then if you have
"Create folder for separated layers" option enabled, it will be erroneously
placed into the folder. The same will happen if this morph lies on the layer
which has a clip over it.
- There can be errors while converting a text which has symbols of a national (localized)
alphabet.
- If a SWF file does not contain any information about the font, then conversion will lead to
the following erroneous texts: "??????".
- Some problems are still possible while converting SWF-ActionScripts to FLA-ActionScripts.
-
When decompiling a motion tween, you need to play with "Motion" settings, otherwise it can lead to
decompiling one motion tween into several tweens, or vice versa into the tween that uses incorrect
trajectory.
- Some shapes that have unacceptable fills can be decoded incorrectly.
Usually such files were not created by Macromedia Flash. The unacceptable
fill is the one that is present within a non-closed area that has gaps along its contour.
-
Files created with ScreenFlash are not converted totally correctly. Actually, the SWF files created with this tool
do not comply with Macromedia standards.
-
Morph shapes have beginning and ending states. When placing a morph shape on
a frame its intermediate state is used. It means that morph shape can be rewinded/forwarded
into any of its states in SWF. However, it is not possible within FLA format.
They are placed on the timeline and always run from their beginning state to the ending one.
- When you compile your FLA file into SWF the first time, the hierarchy of the layers
gets deformed. This peculiarity is important only for Morphs. When a morph is placed
on a frame its state is remarked and written, it leads to the problem when a series of morphs can be "split"
into several layers. Such frames cannot be correctly converted into FLA at this stage.
- FLA format allows placing as many objects on one layer as you want, however,
SWF has a limitation of 1 object only. So when converting SWF into FLA objects will be placed into separate layers.
- SWF file may contain font, which is not installed in your system. In this case Flash will ask for a
replacement when you open a converted FLA.
- In FLA files actions for buttons are set when you place them on frames.
In SWF files actions are stored in buttons themselves, that's why each button will be represented as a separate instance in FLA,
even if they are different in ActionScript only.
- Files compressed with algorithms other than ZLib compression are very likely to lead to erroneous conversion.
|
|
|
|