JPEXS Free Flash Decompiler Issue Tracker

If you are looking for the decompiler itself, visit https://github.com/jindrapetrik/jpexs-decompiler

: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means waiting times in the issue tracker are very long and mostly depend on community. Sorry for the inconvenience.

List of issuesList of issues

#1435 Adding a DefineScalingGrid tag to a DefineSprite tag fails, and will corrupt the SWF when it is saved
Date created:
Type: bug
Visibility: Everybody
Assigned to:
State: new Help

> What steps will reproduce the problem? Open any SWF with a DefineSprite tag inside. Right-click the DefineSprite tag and attempt to add a new DefineScalingGrid tag. Save the SWF. > What is the expected output? What do you see instead? Expected result: the new DefineScalingGrid tag appears inside the DefineSprite tag, before its first frame, and can be interacted with and edited as normal (i.e. exactly the same as a DefineSprite that already had a scaling grid). Saving the SWF should produce a valid file: FFDec should be able to close and reopen it. Actual result: the DefineSprite tag is shown in bold as if edited, but the new DefineScalingGrid tag doesn't actually appear. However, saving the SWF will produce a corrupt file. In some cases, this corrupt file's contents can be seen in the Hex Dump view but not in Resources; in other cases, even Hex Dump is blank. From the Hex Dump, it's clear that the DefineScalingGrid is being inserted after the DefineSprite's END tag, and the DefineSprite tag's length is not being updated to include the DefineScalingGrid tag. > What version of the product are you using? Is it "nightly build"? Which operating system do you have? v10.0.0 Nightly build 1655, running on Windows 10.
user
Workaround for anyone experiencing this issue: export as XML, add a DefineScalingGrid element as a next-sibling of the DefineSprite element, and import again. If you can find a file that already has a DefineScalingGrid, export that file as a reference. Note that while XML exports/imports appear 1:1 in my use case, there is an open bug suggesting that they aren't always 1:1.