Ashley's Recent Forum Activity

  • 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.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Can't reproduce on a HTC 10: even very small touch movements are tracked by the drag & drop behavior. There is no minimum distance implemented in our engine, but it's possible some types of touchscreen require a small amount of movement before it starts registering a moving touch. I presume this is the issue, so closing.

  • Thanks, should be fixed in the next release.

  • It would be very useful to know if a specific release caused a change, but given that we have not touched the saving code since r250, I would suspect this is actually a sporadic issue that has been mis-attributed.

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,830,653 followers

Connect with Ashley

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x126
    Coach One of your tutorials has over 1,000 readers
  • x74
    Educator One of your tutorials has over 10,000 readers
  • x5
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x44
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs