Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove data that should be computed on the fly from the XML files outputed while unpacking a sprite! #7

Open
PsyCommando opened this issue Jan 24, 2015 · 2 comments
Assignees

Comments

@PsyCommando
Copy link
Owner

We don't want to let users handle those, as they're virtually useless to them, and not setting them correctly can mess up everything !

The ones that should be removed so far are :

  • XOffsetBit5 / IsLastMFrameInGroup (Can be deducted from the ordering of the frames in the XML file)
  • Is256Colors ( Can be deducted from image file's bit depth )

The others considered for removal are:

  • Meta-Frame resolution ( Can be deducted from image file )
@PsyCommando PsyCommando self-assigned this Jan 24, 2015
@PsyCommando PsyCommando added this to the ppmd_gfxcrunch milestone Jan 24, 2015
@PsyCommando
Copy link
Owner Author

Only the image resolution is left, and once the way resolution is stored in WAN sprite is better understood it will go away as well !

@PsyCommando
Copy link
Owner Author

A tradeoff was made with the image resolution. If a mismatch between the meta-frame and its corresponding image is detected, the meta-frame will be automatically fixed by the application. However, it will only work if the image's resolution is one of the valid resolution!:
8 x 8
16 x 16
32 x 32
64 x 64
16 x 8
8 x 16
32 x 8
8 x 32
32 x 16
16 x 32
64 x 32
32 x 64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant