Ashley's Forum Posts

  • I think it should be OK - have to try it and see, but it shouldn't use too much memory.

  • It's a lifetime license, but it will only apply to Construct 2 - when we release Construct 3 that will be a different product, but we're not even planning it yet, we have a lot of work to do on Construct 2 first.

    We can't confirm any plans about an EXE exporter at this stage I'm afraid, we still have a lot to do on the HTML5 exporter.

    The same goes for Android, but you can already get games running on Android via the browser, or by PhoneGap (currently experimental, and hopefully should work better when Android 4 comes out).

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Oops, that message appears on PhoneGap by accident, the latest build did that. Download this modified preview.js and paste it in to <install path>\exporters\html5 and it should fix it.

  • You do not have permission to view this post

  • You do not have permission to view this post

  • Yeah, hopefully we'll add posting and XML posting in future, it's just we have a long todo list right now! Hopefully it has enough basic functionality for the time being.

  • There's nothing special about common.js, it's just copy-pasted to the top of both the edittime and runtime script files. So if you have function FooBar() { ... } in both edittime and runtime, cut and paste it to the common file and it should be available in both.

    Edit: oh, but those functions end up in the global namespace. It would be best to create your own namespace in common.js, so it doesn't conflict with any other plugins, e.g. in common.js:

    var MyObjectCommon = {};

MyObjectCommon.FooBar = function () { ... }; // etc

    then in both edittime and runtime you call MyObjectCommon.FooBar(), and it should avoid any name collisions.

  • We are currently aiming Construct 2 at games, so there are some simple features like the two form controls but not much for apps right now. It's something we'll be looking in to in future.

    Reading/writing files to disk generally isn't allowed in a browser, although there are some new HTML5 features that allow writing files to isolated storage. There's also the WebStorage plugin in C2 you could try out. Also, ini is a really old and long obsolete format from Windows 3.1 - I'm surpised it's lasted as long as it has! If we added equivalent features it would surely be XML.

    In other words, app development in a browser is probably a little different to what you're used to, and we're missing some features right now, but we hope to patch it up soon.

  • Yep, definitely sounds like a graphics card driver problem. You'll just have to find a way to update your drivers I'm afraid.

    I know it's not easy - some of these vendor sites are so badly designed its almost as if they're trying to stop you, but you have to hunt around a bit and hopefully you can find the right one after a while...

  • You do not have permission to view this post

  • Not only that but it also looks like Microsoft are giving up on Silverlight! HTML5 is definitely the future :)

    Edit: as for Adobe, I think it's just the mobile Flash player they're discontinuing. I think they're going full steam ahead with the desktop Flash player - but if they're abandoning mobile for HTML5 how long is it till the desktop Flash player follows?

  • Going to close this one again - let me know if it happens again in r67 or newer.

  • OK, closing as fixed in r67. Man am I glad to close this one.

  • Should be fixed in r67!

  • Should be fixed in r67.