Ashley's Forum Posts

  • What problems have you read about?

  • From the manual entry:

    A wake lock might only be granted in a user input trigger, such as On touch end.

    It's like with audio playback - you can't automatically do it on startup in a web browser to prevent abuse.

  • It's a known issue - there's a workaround here in the mean time.

  • Try using the Platform Info object's 'Request wake lock' action.

  • Preflight requests are a normal part of CORS and can happen in a variety of other circumstances. I think it's best just to accept it and update the server configuration accordingly, and then it shouldn't be an issue again. We could add some kind of setting for this, but as I mentioned preflight requests can happen in other situations so I think it's best just to get the server configuration to cover preflight and then all cases are covered.

  • These aren't default values, they're pre-filled autocomplete entries. You can use autocomplete in the SDK with the autocompleteId property for string parameters. The SDK doesn't currently provide a way to provide pre-filled entries like this, but I'm not aware of any use case for that currently - File System is a one-off case.

  • Web Workers don't have access to the document and so can't directly read the URL parameters. In this case the easiest solution is just to turn off worker mode in Project Properties, and then your code runs in the DOM with access to the document. If you then use JavaScript to start your own Web Worker, that won't be able to directly access the document either, but you can then read whatever URL parameters you want and post them to the worker.

  • It looks like the problem is that since the AJAX plugin added support for 'On upload progress', cross-domain requests have changed from simple requests to "preflighted" requests. These make an OPTIONS request before carrying out the real request. It looks like your server is configured to respond with Access-Control-Allow-Origin: * for GET requests but not OPTIONS requests, so it now fails with a CORS error as the preflight request is not allowed. So I don't think it's a bug, it's just that the way requests are made has changed, and you now need to update your server configuration. There's more information in the MDN guide on CORS and I added a note about this to the AJAX manual entry.

  • You can use any past release at any time - you can find them all on the releases page. The main URL at editor.construct.net will always load the latest stable release, and as new users should get the latest version, I don't think that will ever change.

  • The only change was the addition of the 'On upload progress' trigger, which should not have affected any existing projects at all. I'm afraid it's impossible to say any more without the details provided by a bug report, as we need that information to be able to investigate.

  • This is what the Addon SDK is for.

  • Try pressing F12 and check for any errors in the browser console.

    You might want to check your server cache settings as well - it's possible the server is serving mixed content (i.e. some files from an old version, and some files from the new version) which would likely break things. You should make sure there isn't some caching setup that might do that.

  • It would be nice, but it's a major project - it would involve running the TypeScript compiler and language service in the editor. It'd probably involve upgrading the script editor as well. If I could snap my fingers and it was done, I'd definitely do it, but things are usually not that easy! In the mean time using an external editor like VS Code is a pragmatic approach that should still work pretty well. You could also file a suggestion for this as if it collected a lot of votes we'd be more likely to prioritize it.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • I don't think there's anything wrong on our side - it looks like the connection on your end is being closed. My best guess is browser extensions, overzealous security software, privacy settings, or VPNs interfering somehow.

  • It seems to be working fine for me. Try disabling any browser extensions you have installed - those can sometimes interfere with Construct and break it. Also try pressing F12 and see if there is a more detailed error message in the browser console.