Due to staff holidays contacting individual developers could take a few weeks. As always the fastest way to get a response is to file a report following all the guidelines on the public bug tracker.
Due to other ongoing work and staff holidays please allow a couple of weeks before getting a response to an issue. Please also note if you have not filed an issue following all the bug report guidelines, it can take considerably longer to resolve issues.
I'm not sure, we just fixed a bug. Have you tried it?
Sorry, it turns out the server-side change wasn't actually live yet when I first commented. It should be now (for real hopefully!)
See the video for the last release: youtube.com/watch
We had to make a server-side change for this release. It should be working now.
Chrome on iOS is a wrapper for Safari because Apple don't allow other browser engines, and Apple don't support Bluetooth in Safari yet. Hopefully they'll add support for it in future.
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.
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.