Please file an issue for this. It's far more likely we will do something about it if it's written down. All the fixes to themes on this release where issues in our tracker.
github.com/Scirra/Construct-bugs/issues
If you have any feedback you can just post it in the forum, it will likely end up becoming the feedback thread.
When you make changes to instances in a hierarchy where a template instance is the root, those changes should be applied on the corresponding instance on the replicas.
That is, if the template and the replicas match up perfectly, if they don't the changes are not applied because there is no way to guarantee the instance in the template has a corresponding one in the replica.
Making changes that make a connection, remove a connection or outright delete an instance from a template's hierarchy will make all replica's match the template. I think we will add a new property to templates to decide whether or not to use this behaviour.
I think in most cases this is the desired behaviour, after all the replicas are supposed to match the template... but I can see how in some cases someone might want to make sure a replica does not update automatically with the template or a template does not propagate hierarchy changes automatically.
We figured it was better to wait for feedback on this one.
The flowchart tools work the same as the layout view. SHIFT + Click to select multiple things, CTRL/META + Drag to clone a selection.
You can also clone by copying and pasting a selection of nodes.
"In Quartic" and "Out Quartic" eases were producing an unwanted result at the beginning and end respectively, a sort of mini "bounce" effect. Turns out they were just set up incorrectly.
I think there was a regression in this release from trying to fix another issue. It should be fixed for the next beta. Still, it would be worth trying to reproduce it.
When you compare code and events, events handle a lot of the heavy lifting so you can do a lot more with a few events than what you can do with a few lines of code. In fact, a few lines of code won't get you very far.
The free version is meant to serve as a test drive and with the previous limit to the lines of code you could use, it wasn't really good enough to try out the feature.
The expression was implemented because of this suggestion construct3-21h2.ideas.aha.io/ideas/C321H2-I-438
Normally we prefer if people report any issue to our tracker, but this one was easy enough to fix it right away for the next beta.
You mean seeing the layout of the original global layer?
This is not a bug. Text input instances are HTML form controls and as such are always on top of all other content which is drawn to the main canvas, such as Sprite instances or Backgrounds.
construct.net/en/make-games/manuals/construct-3/plugin-reference/text-input
The feature is still set to be experimental on stable releases. You can turn it on by toggling the "Use experimental features" checkbox in the main settings menu.
It has to do with the dictionary editor, which is slightly different to the array editor and is not working with the changes to be able to resize the headers.
Namely because the dictionary editor does not have a column header.
What you were trying to do is an expected use case, I just didn't think about trying it myself as I was developing the feature. This happens quite frequently and it is hard to avoid it.
It is the main reason why we have frequent beta releases and why we waited for a new beta cycle before showing this feature. By the time we make a new stable release, all of these small issues will be sorted. As for the people that are interested in trying out the beta releases, the fix will be available soon, so it's ok to just forget about it.
Member since 24 Apr, 2015
The official blog for all things Construct and Scirra run by our employees!