Hm, I thought Dines' system some more. I realized it lacks some flexibility - if the included event sheets are specified in that additional box, you can't arrange how the includes are in the layout main code. In some situations the run order of the events does matter. However, the events separated into different sheets don't usually have too much relations, so does the order matter so much?
As you might read from my previous post, I had some kind of vision of "unified" Project bar. It could have the layouts, the resources and the "general" event sheets there. And event sheets could be included in the event editor, like now. Maybe there could be a restriction, that the layout-specific event sheets couldn't be included, I dunno about that.
Edit: Oh, and I have a questions for Ashley: Is there need for global objects? (Or, what I really want to ask, is there need for non-global objects
) What they actually are in Construct? How they differ from normal objects? What I'm thinking, global objects are some kind of relic of "thinking in MMF", I think that every object should be "global" so that there wouldn't be hundred and one types of objects which actually are the same, copied to different frames.
Or is it only my who is thinking in MMF
? What does globality mean in Construct?
Edit 2: Apparenly, it was only me
. Did some testing and in two different layouts it considered copyed sprite as the same. So objects are global in a way. But what does the "globality" in Construct mean then?
And is there some GUI for inserting objects from the other layouts, except for copy&paste? And what about objects without "body", like Keyboard and Mouse?