Ashley's Forum Posts

  • It's by design: they work the same as Array and Dictionary, which is that you can put them in a container with another object to have per-instance state. So just like you can put an Array in a container with a Sprite to have per-instance array data, you can put a Flowchart Controller in a container with a Sprite to have per-instance flowchart state.

  • You do not have permission to view this post

  • But at the same time I don't want to take a risk and turn it on forcibly

    If it used to be on, then changing the setting to force it to be on just means it's doing the same thing it was before.

  • The worker mode "auto" means Construct decides automatically, and we sometimes tweak the way Construct decides to work around things like known issues. You can change the setting in Project Properties to either "yes" or "no" to indicate a specific setting, but you then might run in to some kind of problem that "auto" mode was trying to avoid.

  • It might be over the upload size limit. Try uploading a smaller file.

  • You're right, the return type should be IWorldInstance | null as it is for the equivalent ICollisionEngine method. Thanks for spotting, that's fixed for the next beta.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Functions in Construct's event sheets only support string, number or boolean types. There is not an "any" parameter type so you cannot sometimes pass a string and sometimes pass a number to the same parameter. You can work around this by having a string parameter, a number parameter, and a boolean parameter indicating which parameter should be used.

  • I've removed the reference to 'Is supported' from the tutorial and removed the use of the condition from the example projects for the next release. As noted you never need to check this any more, as in practice it is always supported.

  • You do not have permission to view this post

  • If you want to tell apart mouse and touch input, I'd recommend disabling 'Use mouse input' on the Touch input and making separate sets of events for input. You can do things like call functions to avoid duplicating logic. The 'Use mouse input' setting is intended as a shortcut if you don't need to tell the difference between mouse and touch input, so if you do, it's not really the right setting to use. Any other approach I'd say is pretty much a hack and may well not work reliably, as some devices support both mouse and touch input, so the only way to truly know if an input is a mouse or a touch input is to handle them separately.

  • You do not have permission to view this post

  • You do not have permission to view this post

  • You do not have permission to view this post

  • You do not have permission to view this post

  • Construct is browser-based software, but you can install it as an app from some browsers like Chrome and Edge. See this manual entry for more details.