Suggestion number 1 (solved):
Hey! I've been searching throughout the forums and couldn't find anything solving this actual issue, so here it goes:
I was wondering if it could be possible for the boys, not knowing at all if it's impossible because of the engine or something else, to add a special event, "Previous layout", an event I've envisioned as a simple "If" object with which you can select the Layout you're referring to, and so any action specified with this will simply activate when the previously visited Layout (previous compared to the one showing at the moment) is the quoted one.
I think that might solve some problems I'm having with the performance-oriented resizing I'm applying to all my really (really) big levels, thinking it would be great to make them into "tinier" parts and create one layout for each of these parts. But that idea, which I don't know if it's good or not, seems difficult without that kind of aid, because changing from one layout to another restarts the whole game experience.
Thank you all very much. Keep up such a great work.
Suggestion number 2:
Whenever I open the program to start working, Construct 2 loads in the upper bar all the layouts first and then all the events sheets. My workflow is better when every Layout gots its own Event Sheet at its side, and so changing between the actual scene and the event editor is fast and convenient. As in:
<img src="http://i46.tinypic.com/jjlg8h.png" border="0" />
Would it be possible for us to set two differents startup loading configurations, 1. All.Layouts + All.EventSheets; and 2. Layout1+EventSheet.1+Layout2+EventSheet.2...?