Ashley's Forum Posts

  • As far as I could tell, it looked identical to Chrome on Windows 10. For bug reports, the simpler is the better. Ideally there should be no interaction necessary, no unrelated objects/layouts/events, and no other issues mentioned. This will minimise the chance that your report is misunderstood.

  • Note if this is ultimately caused by this issue then hopefully fixing that will correct this too.

  • Thanks for the minimal repro. It looks like a collision bug fix in r257 has broken some kinds of collisions. Hopefully this is what is behind the other reports of issues in r257. Should have it fixed soon.

  • It is incredibly difficult to deal with bug reports like this. Please see the bug report guidelines. Is there any way you can reduce the project or isolate the part that isn't working?

  • No project provided so tested Ghost Shooter. Can't reproduce, it works fine. Please follow the bug report guidelines to ensure we can fix the problem you are reporting. Closing.

  • In Construct 2, projects cannot be opened if they use any third-party addons that are not installed. Having to go and find the addon and install it is a significant complication, we might end up with a different version of the addon, and the problem may be caused by the addon in which case we can't support it. Please co-operate with the bug report guidelines to ensure we can deal with the report effectively.

    I'm afraid the link you provided covers unrelated technologies.

    I tested as a debug APK on a HTC running Android 8. I could not reproduce any issue, it all looks fine. So I doubt this is really caused by Android 8. Also, normally issues which only reproduce on certain platforms/devices indicate a problem with that platform/device: the fact it works in some places usually means our code is correct, but a bug in the platform/device is what breaks it. On that basis my best guess is this is some kind of GPU driver bug, which is the most common cause of any kind of graphical issues. If that's the case I'm afraid there's very little we can do about it. Even if not, there's very little we can do without a way to reproduce it ourselves 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

  • Any significant software project with a bug tracker will have some long-term open bugs - that's normal. Unfortunately sometimes there's just nothing quick or easy that can be done about an issue. It can be difficult even to make a useful comment, since often it's not clear what the problem really was until it's fixed. Still it's useful to have them logged as known issues, and the team does go back through old issues from time to time, especially when dealing with potentially similar issues or changes that might affect them. So while we may not be able to say anything useful about every report that is filed, we do still appreciate good bug reports and it's useful to have them there.

    The best thing you can do to help make a bug report fixable is follow the bug report guidelines as closely as possible. For example if it's not already reduced, reduce the project to the absolute minimum possible - an ideal sample project has maybe <5 events and <5 objects.

  • The main issue is you need a server to send the push notifications, which means hosting costs, server-side code, etc.

  • If all browser tabs/apps ran even in the background, it would absolutely hammer the battery life of the device. So operating systems and browsers are very strict about what can run in the background, for good reason: saving battery. Nobody wants an app to drain all their battery and many users will uninstall any apps they find wasting battery (and possibly give them a bad review).

    The question here is, what are you trying to do?

    If you want to play music in the background (e.g. music player app): you can enable playing in background on the Audio object.

    If you want to simulate real-world time passing in the game: wait until the app wakes up, measure how much time it was asleep for, and then simulate that much time passing. That has the same effect and doesn't waste loads of battery.

    If you want something else... what is it you're trying to do?

  • You do not have permission to view this post

  • This is a potentially big change. The docking bars code is very complicated, is recursive to allow arbitrary nested layouts, and already has a number of special cases for things like mobile support and popup windows. It is generally very difficult to make changes to. In order to expedite the release of C3 we deliberately dropped some features we believed were little-used (including others than this one, which so far we haven't heard complaints about). I haven't seen many other users asking for this, and this is backed up by the feature request not having many votes, and so given the complications around implementation, I'm afraid it's not a priority right now.

  • OK, hmm, well not sure how to reliably get that with the available NW.js APIs. I've posted a message on the NW.js group to ask about it.

    In the mean time I think a one-off setup after install to choose a file path would be an acceptable solution.

  • Yes, third-party addons will need to be ported to the new C3 runtime. I'm afraid it's completely different - there are pretty much no lines of code that are the same - as it's been a total ground-up rewrite. This rules out automated conversion.

  • The AppFolder expression returns the folder of the main executable file that started the app. On mac this happens to be in a subfolder. So it's working as expected, it's just the folder structure of an app is different on mac. (I can see the naming might be misleading, but this is how it's implemented right now.)

    What are you trying to do with the AppFolder expression that needs it to point to the folder containing the .app subfolder instead?

  • The project link is not a public file so closing. Please make sure issues include a publicly accessible .capx file.