Ashley's Forum Posts

  • Construct 2 does have an update notification! It just tells you when a new version is available, but won't download it for you (see that thread).

    However sometimes I delay setting off the autoupdater till a few days after a build is out. If there's a big problem I won't trigger the autoupdater at all and will wait until the next build when it's fixed instead. If a few days have gone by and the release seems to work OK, then I set off the autoupdater. Then, it takes up to 24 hours for the software to check for an update again and alert you.

    So you should see prompts even if you never visit the site.

  • OK, it's on the todo list now!

  • Sorry, we really don't have the resources to work on anything but the most important features that affect the majority of users, and Facebook is obviously one that nearly everyone can take advantage of.

    If you're building your own website with an API, there's nothing stopping you making your own integration plugin with the SDK. So we won't make an official one, but you're free to make your own.

  • As I mentioned in another post HTML5 audio simply can't support this yet, but there may be features on the way which do.

    Browser support for audio right now is pretty poor. There are clicks and cut outs, and these are the fault of the browser - there's nothing we can do. Just keep your browser up to date with the latest version and hope they fix it soon.

  • This is not currently supported by HTML5 audio. However, new features are in the works which would allow for this kind of audio processing. I think modern javascript engines might actually be fast enough too, considering its pretty much all compiled to machine code now.

    The new audio APIs are probably about six months away, and then there's no guarantee all browsers will support them (Internet Explorer is particularly slow and reluctant to adopt new standards). So you'll probably just have to wait it out for now I'm afraid.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You do not have permission to view this post

  • Hi plugin developers,

    Just a heads up - we're getting bug reports that projects don't work after exporting with minifying enabled. I'm pretty sure this is because of third party plugins.

    The minifier renames object properties. If you mix object.prop and object["prop"] syntax your plugin will probably break the project on export. From the SDK documentation:

    hen exporting, Construct 2 gives the user the option to 'Minify script'. This runs the common and runtime scripts through Google Closure Compiler's ADVANCED_OPTIMIZATIONS mode. This imposes some limitations on what scripts can do. You must obey these limitations when writing your plugins, otherwise your plugin will be broken on export. More details can be found here (http://code.google.com/closure/compiler/docs/api-tutorial3.html).

    The main thing is to always use dot syntax (Object.property) rather than bracket syntax (Object["property"]). All properties using dot syntax are changed by Closure Compiler, but none of the properties in bracket syntax are changed. Therefore, if you use Object.property in one place and Object["property"] in another to access the same property, the plugin will be broken on export. You may still use bracket syntax (e.g. for a dictionary of user-inputted strings) - just be aware of how Closure Compiler will transform the code.

    Remember the edittime scripts are not passed through Google Closure Compiler, so you can write them how you like.

    Please double check all your plugins correctly minify on export! And don't forget to read the documentation! <img src="smileys/smiley1.gif" border="0" align="middle">

  • It seems minify will change the name of properties in an object.

    Yes, this is how the minifier works, and it's talked about in the SDK documentation.

    When exporting, Construct 2 gives the user the option to 'Minify script'. This runs the common and runtime scripts through Google Closure Compiler's ADVANCED_OPTIMIZATIONS mode. This imposes some limitations on what scripts can do. You must obey these limitations when writing your plugins, otherwise your plugin will be broken on export. More details can be found here (http://code.google.com/closure/compiler/docs/api-tutorial3.html).

    The main thing is to always use dot syntax (Object.property) rather than bracket syntax (Object["property"]). All properties using dot syntax are changed by Closure Compiler, but none of the properties in bracket syntax are changed. Therefore, if you use Object.property in one place and Object["property"] in another to access the same property, the plugin will be broken on export. You may still use bracket syntax (e.g. for a dictionary of user-inputted strings) - just be aware of how Closure Compiler will transform the code.

    Remember the edittime scripts are not passed through Google Closure Compiler, so you can write them how you like.

    If code like you pointed out occurs in official plugins, behaviors or scripts please do file a bug report. However, if it's in third party plugins or behaviors you should tell the developer about it, not us... and then tell them off for not reading the documentation and writing a broken plugin <img src="smileys/smiley1.gif" border="0" align="middle">

  • Looping works in some browsers but not others, I can't remember. Just make sure you test it so on browsers which do support looping you don't get the music playing twice.

  • Sorry, browsers have really bad audio support at the moment. All you can do is keep your browser up to date and hope they fix it soon. There's nothing much we can do to fix it.

  • Ah, I see the confusion now. You've missed the 'initial visibility' property :)

    Layers have two properties:

    Initial visibility - only affects the runtime

    Visible in editor - only affects the editor

    The checkbox is a shortcut for the "visible in editor" option. So if you want to change the runtime use the "initial visibility" option! <img src="smileys/smiley1.gif" border="0" align="middle" />

  • Well, it's always tricky to fix issues I can't reproduce... no way to know if I've fixed it. Still, I'll revise the http server code and see if I can come up with something...

  • Works fine for me in all browsers in both preview modes: test

    This is why you should always provide a .capx: it seems to be working fine here, so presumably you're doing something else you hadn't realised that is causing a problem.

  • Good point, it's a useful event that is missing. Added for next build.

  • Caer, try one of the things zenox98 suggested.