Ashley's Forum Posts

  • You need to request permission before using motion/orientation.

  • As ever, without a project to look at, all I can say is it should work, and if it doesn't, the error message it tells you is presumably correct in its diagnosis and you should do what it says.

    I also noticed that functions are global now, you can call them from any eventsheet even if they are not attached, is this by design or a bug?

    This is by design.

    • Post link icon

    This looks like a duplicate of this thread so closing. Posting the same thread is against the forum rules, please see the Forum & Community guidelines.

  • As I said, if you can reproduce a case where Construct seems to get it wrong, please file a bug following all the guidelines. It's the usual way that we deal with problems and the process is designed to maximize the chance we can fix the problem.

  • I manually removed a few files from our releases that aren't needed for the purposes of Construct, including:

    • pnacl (Portable Native Client), a browser plugin that Construct doesn't use (and Chrome will remove themselves in future anyway), including the .nexe file
    • All locales other than en-US
    • The tools chromedriver, nwjs, payload (these are separate to dev tools and aren't generally needed in Construct)

    I did ask the NW.js developers for info about which files are essential, but they said to just use trial and error, and I've noticed the set of files changes sometimes between releases too. So basically you can find out which files are essential by deleting them and seeing if the app still starts! I'd watch out though since some files may be optional and could break features. For example the app may still start if you delete notification_helper, but then it seems likely notifications won't work any more. So it's worth doing a little research to try and figure out what the purpose of the file actually is, and if it doesn't sound important and the app starts without it then it can be removed.

  • Actually, I can't find anything that's wrong, it all seems to be working correctly. If Construct is doing something like inconsistently copying some properties but not others, please file a bug following all the guidelines.

  • The instance properties are stored in the instance. So if you delete it, those properties are gone.

    When you create a new instance, Construct will copy the properties of an arbitrary existing instance. If none exist, it will try to use the properties of any previously deleted instance. If there are still none, you get the defaults.

    So the properties you get depend on whether there are other instances in the project, or whether you previously deleted instances.

    I think there might be a small inconsistency in how behavior properties are handled though, they don't seem to refer back to deleted instances. I'll look in to that a bit further.

  • I've updated the original post with the new approach to releases as I outlined in January. This means you can now download your own NW.js versions to use with Construct 3, allowing NW.js updates to happen without our involvement. It also means for the first time you can choose NW.js platforms other than Windows 64-bit, such as Windows 32-bit, Mac and Linux. Note however that no testing has been done with the editor the NW.js versions of Mac or Linux, so I can't guarantee how that will work. However NW.js has good cross-platform portability so in theory it should work the same as on Windows.

    Hopefully this new approach works out smoothly; let me know if anything seems wrong.

    Note NW.js 0.45.0 based on Chromium 81 came out this week, so to update to that version, use the new approach. New NW.js versions, including beta and patch releases, are announced on the NW.js blog and on their @nw_js Twitter account.

  • Try using the Share object to share the video instead.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It's not currently supported. All supported features are documented in the scripting reference, and if it's not there, you need to use the event system instead.

    These do sound like they would be useful in scripting though, so I'll look in to adding them for a future release.

  • NW.js doesn't support MP3/MP4. This is why we recommend you use WebM. Construct automatically converts all imported audio to WebM where possible. WebM works everywhere so you won't have this type of problem with it.

  • It's best to provide context when asking questions, because the answer depends on what your overall end goal is.

    If you need to do this for lots of functions, the best approach is probably to make a Cordova plugin, and a Construct plugin that talks to the Cordova plugin.

    If you only need to call one function and just want a quick shortcut, you can call functions from JavaScript. So you just need a way to make the WebView run that JavaScript. The WebView class should have a method for running JavaScript.

  • Last I tried they were working, if not please file a bug following all the guidelines as usual.

  • Android has had support for both formats for years!

  • I've never heard of such a platform. I didn't think any existed. Which platform is it exactly? If it turns out it does actually support OGG or M4A - as all known platforms have for years - then the problem doesn't need solving.