I'll give that a try, thanks!

"Auto mirror" appears to do a bit of what I want, but I'm not sure if that's what you meant...

I've got a sprite set up for 8 directional movement. If you move right, the sprite is the right way up. Moving left, however, flips the sprite vertically.

I suspect this is due to my current lack of understanding of how Construct works, rather than a bug.

Thanks.

As per posted by dfyb:

will we [still] have the option to build a single .exe or identify what we want stored in .exe and what we want stored externally? i like the option to store images externally (makes replacing sprites lots easier) but i'd like to have control over what's called and what's stored within the .exe.

Game Editor has a data directory which can store all resources used by a Game Editor project. Something similar here would be useful for an option along these lines.

It'd also be nice if - either as external file or exportable - they're in a human readable(ish) format. XML maybe?

Yeah, it's the SUSE Geeko. As far as I'm aware it's not under any kind of CC licensing arrangement.

Dunno if Novell'd like the use of their trademark for it!

Useful! Thanks for the info. So in theory you could have a layout sheet(s) with nothing in them but required sprites and define events in there, and then include those elsewhere? Interesting.

Sounds like I'm going to enjoy this...

But the point is, if event sheets are tied to a layout only, then for another layout you'd need to recreate those events from scratch. This seems an unnecessary duplication of effort, unless you can tie event(s) to object(s) regardless of whether or not those are per-object or per-layout.

Any chance of supplying a ZIP file of these, please?

Can handle OpenOffice.org, Firefox etc without problem. I've got one, and it's a nice little bit of kit.

Is that all you wanted? A quick and easy way to paste objects between applications and have their events go with them?

If it means I could copy and paste behaviours and events for objects easily, then yes.

Also, it could make object-based inheritance easier. Say you wanted a type of object to have certain behaviours or events. You could have a base object, with something to identify it as a kind of object which other objects could inherit behaviour/events from.