Ashley's Forum Posts

  • It should work. I've tried it many times in the past and verified it does work offline.

    If it got somehow broken at some point, please file an issue following all the guidelines. Please note any report about C3 not working offline must start with these steps:

    1. Clear storage/browser data/etc to revert to clean (uncached) state

    2. Load C3 while online and wait for the "ready to use offline" notification.

    3. (Whatever further steps necessary to reproduce the problem)

    Several times in the past people have skipped step 2 and as far as I saw it was working fine.

  • It should work. It's hard to say more without further details. Try making sure all OS and software updates are installed.

  • There's nothing special about C3, it's a global variable and so you have to reference it with self.C3 like all other global variables.

    However if you look at the latest addon SDK downloads, they put const C3 = self.C3 at the top of the file scope. This lets you reference C3 without self, because it makes it a local variable. You can use this technique for any global variables that are frequently used to avoid having to repeat self. everywhere. The addon SDK documentation assumes you're working with the latest SDK download which lets you use C3 without self.

  • Families and objects pick separately. 'Create object' picks the created instance. If you want to use that instance in later actions, it must be an action in the same object.

  • Say that I had 10 lines of text, if I used sprite fonts, would EACH of them require a copy of the graphical font?

    No, they all render from the same source texture that is loaded once.

  • We need a behavior that pairs objects for automatic picking, but can reset the relationship.

    The reason containers enforce the same number of objects is it's the only feasible and efficient way the picking-together system can be implemented. Any kind of other "pick together" feature that doesn't have the same restrictions as containers, would necessarily be very complicated (and therefore probably buggy in all sorts of situations), and fundamentally slow. And so then if you used it a lot and your game ended up slow, you're stuck, there's nothing you can do about it. I would strongly prefer to avoid implementing features that can end up being traps like that - the entire engine is designed to always be reasonably efficient even in the most extreme projects.

  • Ok, what I would like to know now is if adding a child will do automatic picking like containers do?

    No, that's what containers are for.

    Also, containers can only do that automatic picking because of the restriction around creating and destroying the container together. This enforces that there are always exactly the same number of instances of each object in the container, which is what allows the engine to be able to pick them all at once. If we made scene graph do that, we'd also need to reimpose the same restriction - and that would remove the ability to use scene graph dynamically (e.g. attaching and detaching different objects throughout the lifetime of one object). I think it's important to allow the dynamic usage of scene graph.

    Besides, I'd say that well-designed software should not duplicate features in different places. If you want simultaneous picking, use a container. If you want objects to attach to each other, use scene graph. If you want both, use both!

  • They are documented in common expressions.

  • The whole point of containers is if any object in the container is picked, the entire container should be picked. So it should work - if it doesn't, please file an issue.

  • You can also request a wake lock in the Platform Info object.

  • Oh dear, if the swipe is a system level action, normally that means it can't be overridden 🙁

    I think you can change the swipe gestures in the system settings though?

    We have similar trouble on iOS, since Safari seems to handle side swipes as unavoidable back/forward navigation gestures. It's difficult to handle this, I was aiming for a similar pattern to the Wikipedia app where you can swipe in the contents from the right, but it seems hard to do this in a web app.

  • On Chrome for Android swiping from the side never tries to navigate forward or back for me. If it does it might be a bug. What browser/device are you using?

    I like the look of the mockup, but the main reason for the UI limitations on mobile is we're a small team with limited resources, and UI work is extremely time consuming to design, develop, implement and debug. To get UI to "just work" and smoothly do what you always expect it to requires a huge amount of work; any cutting corners and it ends up clunky and awkward. Therefore the mobile version is designed to work as closely as possible to the desktop version, involving the fewest changes. Similarly proposals that involve a small series of simpler and quicker changes to move things in the right direction are much more likely to actually be done than a complete overhaul.

  • It should work. If it's Construct that's crashing, please file a bug report following all the guidelines - we need all that information to help, since unfortunately it's impossible to fix problems from a brief description and some pictures.

  • 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

  • At the moment, scene graph has nothing to do with containers at all. We might find ways to integrate them in future, but the situation right now is they are two independent features that are working separately.