Since Construct 2 still requires the layout to have (as I workaround I can create an extra Loading Layout to handle this but anyway...) at least one instance of every object, when working on small single layout projects I usually start with:
On start of layout: ChildObj.Destroy()
I also have an On Create Master Obj : Spawn Child Obj
From what I can tell though, the On Create is firing *before* On Layout Start, causing an object to be spawned then summarily deleted. Is this order of events intentional?
Link to .capx file (required!):
Order of Events Capx
Steps to reproduce:
0. Create Layout -> Add ChildObj and ParentObj to Layout
1. Create ChildObj
2. Create ParentObj
3. Add On Create ParentObj : Spawn ChildObj
4. Add On Start Layout : Destroy ChildObj
Both instances of ChildObj are destroyed.
Only the existing ChildObj should have been destroyed, then "On Create" should have been run.
Internet Explorer: yes
Operating system & service pack:
Construct 2 version: