This bug was introduced in this beta release, it will be fixed in the next beta.
If you are able to reproduce the crash please file a bug report, including as much information as possible.
Are you using a pen input device?
Oh yeah, this only applies for creation, so the instances are created in the same way they show up in the editor.
I guess it is bug, since changing the z order of the parent and having all the children change accordingly seems like a very common and useful use case.
Please, file an issue in our tracker with an example project showing the problem and how you expect it to work. This is a fairly new feature, so we are still working on it.
It means that when you create an instance at runtime along with all of it's children instances, the relative z ordering between them will be the same as the one setup in the editor.
Your description doesn't sound like what was fixed.
This is the bug report for the issue github.com/Scirra/Construct-3-bugs/issues/4313
If you are having a different problem please file a report in our tracker.
We update the manual with each stable release.
The first step was to have something to be able to setup a hierarchy in the editor. We are planning for the editor to preview the connections just like the runtime does so in the future modifying a parent in the editor should make all of it's children follow accordingly.
We still got some more work to do, but I think that eventually we will get to the point were it will be possible to clone an entire hierarchy, both in the editor and the runtime. But as I said, that is still further down the line.
"Scene Graph" is just a fancy name for a system that allows you to nest objects to form a parent -> child hierarchy of as many levels as you want. In the context of Construct, the hierarchy is mainly concerned with 2D transformations, so modifying a parent applies that transformation to all of it's children, in relation to the parent's origin. This includes translations, rotations, scaling and in the future, possibly opacity.
It is usefull to juggle complex relations of objects in a relatively intuitive way (once you get the hang of how it works).
I imagine that a pattern in the case of wanting to have a common origin for a bunch of instances, would be to group them together under a parent with no graphics. This should achieve the effects of having a different origin to the one of the visible root instance.
It's still very early, so that will have to do for now.
I did a quick test and it seems that it doesn't work if both instances are of the same object type. Will look into that, will likely get it fixed for the next beta.
If each instance is of a different object type it should work doing what you described.
It was a design decision. A wrong design decision.
No, everything relating to timelines and tweens is our own implementation.
The Date plugin is a thin wrapper on top of Javascript's own Date object, because of this you can look at that documentation.
developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/parse
Can you file an issue in our tracker explaining the problem? github.com/Scirra/Construct-3-bugs/issues
It is in the start page. Search for "date" and it should show up.
Member since 24 Apr, 2015
The official blog for all things Construct and Scirra run by our employees!