Ashley's Forum Posts

  • Enable advanced minification on export, and it'll be tough to make sense of any of the code.

  • As I said, such technical barriers will make it harder, but not impossible. If the app can decode the details, then they can still be stolen. The app has to decode the details to be able to use them correctly. So they can be stolen.

  • No - Apple maintain strict control over the platform, and your only option is to publish with them, via the way they approve.

  • It can happen to pretty much any kind of software. People have done this with the Construct 3 editor itself. Takedown requests, and copyright law, are your best defences - technical barriers will make it harder, but never make it impossible.

  • For the record, iOS exports are working just fine for me, including in the issue filed by TechBoxNorth . Make sure you open the .xcworkspace file (as documented in the iOS publishing tutorial), and test on a real device since it doesn't work in the iOS simulator due to an iOS bug. (Note that the iOS bug is fixed for a future release of iOS, so the simulator should be working again in the next release or two of iOS.)

  • I think it's some kind of rendering bug in NW.js. It looks like it's working again in the next version of NW.js (0.48+) judging by the nightly builds.

  • You do not have permission to view this post

  • The PhoneGap Build service has effectively been retired, and doesn't work any more. Use Construct's own build service, or do manual builds with the Cordova CLI.

  • As I said before, threads with lots of people talking about a bug are often actually a mish-mash of different issues, and they all get confused together making it even harder to do anything about it.

    Besides, it is impossible to do anything unless we have a sample project and reliable steps to reproduce the issue. So even with a thread with lots of people who really are talking about the same issue, there's usually nothing that can be done until that information is provided.

    The bug report guidelines on the issue tracker are specifically designed to solve both problems.

  • You do not have permission to view this post

  • You do not have permission to view this post

  • Unlimited undo is basically a memory leak, so there needs to be some kind of limit.

    I thought 200 would be enough in practice - C3 has been out for about 3 years and I think you're the first to notice the limit! I guess we could add a setting for that.

  • I don't believe there were any such issues with Instant Games. Do you have a link to the thread you are talking about?

  • Most of the time, when I check an issue based on a brief comment or forum post, it works fine. It's because there is usually some specific circumstances or details that cause the issue but were omitted. Unfortunately this means most such "just mentioning" reports of issues are useless. Repeatedly checking dozens of things every day which all work ends up wasting lots of time, and time is by far our most limited resource. This is why we ask for bug reports to be filed. We also have carefully crafted bug report guidelines written up to help people file useful reports.

  • Those are the two I tried, and they both worked fine for me.