Ashley's Forum Posts

    • Post link icon

    Closing, please only post in English on this forum.

  • It's not currently supported. Drag-and-drop needs to work fundamentally differently with touch input to disambiguate it from pan scrolling. Using one finger to drag and two fingers to scroll doesn't necessarily work well either, since often using two fingers to scroll means putting down and moving one finger first before the second touches the screen, meaning you accidentally start a drag before you start a scroll - and this could happen pretty much every time you try to scroll, which would be irritating.

    Designing these kinds of subtle touch interactions is lots of difficult work and has to be reinvented separately to the mouse input. As a small team with limited resources we've not put in the time yet to implement all of that. This is one of the reasons we advertise the mobile version as being suitable for reviewing and tweaking projects, rather than being a main development environment.

  • Construct already sets the target API level to 29. You don't need to worry about the target SDK, Construct manages that for you.

    The target API level is different to the minimum API level, which is what sets the lowest supported version of Android. You choose that yourself when exporting. Currently Android 5.1 is the lowest supported version.

  • If you run a local web server, it will serve files from your local hard disk. So that solution already covers the case of serving local files. You just have to move them in to the folder that the web server serves.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Why not just update to the latest version?

  • You can host text files on a different web server, and configure CORS to allow it to serve them to your project in preview mode. The AJAX manual entry covers this.

  • either way C3 exports will not work in a export of google play store if they contain or have contained javaScript in the past.

    All C3 exports use JavaScript, because the engine is written in JavaScript.

    We have many users publishing to Android and it seems to be working fine for all of them, so I can only speculate that something has gone wrong for your publishing process somewhere along the line.

  • As far as I am aware, the default settings on Android are to auto-update apps when there is an Internet connection available, and I thought that applied to all markets internationally.

    I still have no idea why there would be any significant number of devices out there that have either changed from the default settings (and have turned off auto-updating apps), or have been offline for 3+ years until they suddenly tried your app.

    Or maybe something else is happening. As I say, it's a mystery and I would be very interested if you could shed any light on this at all.

  • Please file a bug report following all the guidelines - we need all that information to be able to help. Without it all I can say is it should work, and seems to still be working for the vast majority of users.

  • I just tried it and the latest stable release can open Construct 2 projects just fine.

    As ever if you run in to any problems please file issues following all the guidelines, since it's generally impossible to help without all that information.

    • Post link icon

    Please note: the feature will become unavailable in Chrome 85 after Wednesday September 30th. It will be available again in Chrome 86+, due for release next week.

    The underlying feature in Chrome for file system access was previously in an experimental state, and the experiment is ending on September 30th, making the feature unavailable in Chrome 85. The reason the experiment is ending is because it is now enabled by default and available to all websites in Chrome 86+, which is scheduled for release on October 6th. This means there's an approximately one week gap in between where the feature will be disabled in the latest Chrome release.

    The one-week gap is actually an intentional part of the way Chrome handles experimental features. It is designed to ensure websites using the feature rely on detecting the availability of the feature rather than a specific browser, since relying on browser detection has been a long-standing compatibility problem for the web. (Construct of course already relies on feature detection, which it uses to decide whether or not to show the save options - which is why you may see them disappear.)

    As I've previously noted, experimental features are subject to change at any time. (I've also updated the editor for future releases to more clearly state that experimental features are subject to change at any time). If you need to use the feature during the intervening week I would advise to use Chrome Beta, which is already on version 86 and therefore has the feature enabled. Alternatively you can temporarily go back to using the other save options like Cloud Save. Once everyone is on Chrome 86+ in a few weeks, the feature will have fully graduated to a widespread stable release, so there should be no further such interruptions to the availability of local file/folder save options in future.

  • The minify option on export is for extra processing of the built-in runtime scripts. We don't provide any support at all for directly modifying runtime scripts, nor do we want to encourage anybody to do that, so we don't really actually want to provide unminified runtime scripts. Use the addon SDK or the JavaScript coding feature to integrate your own JavaScript code.

  • I'm afraid I've no idea what might help. Apple make Xcode, not us, I don't know what could be wrong or what might help. As I said, you need to be contacting Apple support over this, not asking us.

  • I've already done several iOS exports as part of my general testing and development work, and they all opened fine. To double check, I just did another iOS export and opened it in Xcode 12.0.1, and it opened and ran on an iPad just fine. So it seems to be working fine here. I'm sure Construct is exporting valid Xcode projects and so the problem is not with Construct.

    Anyway, as I mentioned, we can't fix problems in Xcode - that's up to Apple, so if you have trouble, you'll have to contact their support.

  • I'm afraid we can't help with issues in Xcode itself - it's made by Apple and any issues with it need to be reported to them.

    There was an Xcode 12.0.1 update recently which fixed a crash, so it may be worth checking for an update to Xcode.