Event sheets for objects.

This forum is currently in read-only mode.
From the Asset Store
Welcome! I-Spy (Hidden objects) is an educational puzzle that is more than just seek-and-find activities.
  • Apologies if this already exists (or is planned to be implemented soon), but I can't find anything about this in the Wiki (or anywhere else).

    MMF2 supports event sheets for objects (active objects at least, probably most if not all others as well). My (likely faulty) understanding is that Construct only supports per-layout event sheets. If this is so, would it be possible to include lower-level event sheets (e.g., for objects)?

  • We could do, but it only has advantages for copying/pasting objects between applications. I'm not too keen on the idea myself - you can use different event sheets and use event sheet includes to organise your code with modularity - and if objects have events, they just get "hidden" away in a difficult-to-reach and easy-to-forget-about place (imagine having events in an object in the bottom right of a very large layout, or on a locked or hidden layer). Also, it would be implemented simply as pasting all object's event sheets to the end of the main event sheet when the application starts up - so object event sheets wouldn't have any special abilities different to ordinary events.

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

  • 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.

  • It's commonly requested but it's something we don't really want to do.

    However, copy/pasting event sheets would go some way to alleviate the issue, and post 1.0 we have plans to split layouts/event sheets into their own files, so such behaviors could be passed around in small files and then copied in.

  • 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.

  • Ah, you appear to be missing the ability to include event sheets in others.

    Right click in the event sheet editor and select 'include'. You can add as many event sheets as you want which aren't tied to any layout, and include them wherever you want.

  • 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.

  • Yes, that's definitely possible . Once event sheets are stored in their own file (or are exportable etc) it'll be much easier to utilise them for custom object behaviors.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • It'd also be nice if - either as external file or exportable - they're in a human readable(ish) format. XML maybe?

  • Yes, .xml was the format we've chosen .

  • Oh sweet! You guys are working on exportable event sheets?

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)