i really appreciate the new feature, and i was wondering if it was possible to edit the meshes in any other editor, since i've never heard of the .mesh format before.if that's not possible, i'd be interested in the rationale behind inventing another 'proprietary' format versus rolling with any of the existing, widespread & readable ones...

I just made up the .mesh format purely for the purposes of saving from the mesh editor and importing in to games. It's very simple, just a list of points essentially. I can't see how it would be useful to use another format, I'm sure nearly every other editor in the world has much more advanced features which can't be reproduced in a simple sprite mesh. Also, it's not a proprietary format, the Sprite object and its .mesh reading/writing code is all open source and I'd be happy to detail the format to anyone who wants to write format converters or anything like that.

well, the beauty (& potential) of a feature is in the eye of its users :)you never know what people might come up with, so i'm a strong advocate of offering as many entry points as possible.

ashley, it would be very nice if you could spare the time to drop me a note (or wikipage) describing the format; i'd really like to try this, but i'm too much of a scriptkiddie to seriously unravel constructs source code.

A 4-byte ASCII string saying 'HSEM' ('MESH' backwards because I'm lazy about endian) to identify the MESH fileint32: version integer (always 1 right now, reserved for future use)int32: horizontal number of pointsint32: vertical number of points

Then, repeated for each point (number of times = horizontal points x vertical points), in column order:float32: x offset (as a fraction of the original image width)float32: y offset (as a fraction of the original image height)float32: z elevationfloat32: u offsetfloat32: v offsetfloat32 x 4: a, r, g, b for point opacity and filter, from 0.0 to 1.0.