It's automatically used when supported.
"Pick all" does unpick everything, reverting state to as if no events had been run. An action wouldn't work any differently.
It's a convenience feature - if you do need to load the results of 3 simultaneous AJAX requests it would be best to keep using the "On complete" triggers.
They already are - see this thread.
'Wait for previous actions to complete' resumes even if there is an error (i.e. a failed operation is still counted as completed). So if you want error checks you still need to use triggers, or add a sub-event that checks if it worked.
Please see the release notes, it's been replaced.
There are no user-visible changes. It's an internal change only. It has nothing to do with NW.js or AJAX either.
The dropdown looks fine here. Please file a bug following all the guidelines if you want us to investigate.
Alt+Click works for me. Note the editor window has to have focus first otherwise it doesn't get the alt press.
We just swapped an internal storage library for one we wrote ourselves. It should be 100% backwards compatible though so in theory there will be no noticeable changes at all (other than hopefully some rare bugs fixed).
No, it uses our own library.
Also, by default the Android webview automatically updates with no user interaction required; however some older Android 5-6 devices have both years out-of-date software *and* have updates disabled. We still don't know why this happens - presumably some device manufacturers disable software updates, which is irresponsible and leaves users vulnerable to security issues. In this case the user may have to perform a manual update, but as far as we can tell this only affects a minority of devices, and does not affect Android 7+. Unfortunately out-of-date software, and interfering manufacturers, is a general problem with Android itself and affects software development of any kind on Android - switching to a different technology won't make that go away.
We regularly test on mobile and the performance is generally great. As far as we are aware the vast majority of users are exporting to Android just fine. If you experience any crashes or performance issues you can file an issue about it and we'll look in to it - but as far as we can tell right now things are working fine.
HTML5 games can perform great, especially on modern devices. These days we hear very few complaints about performance. Do you have any specific benchmarks or examples?
Member since 21 May, 2007
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.