Ashley's Forum Posts

  • Saving to local files, and saving to folders, depends on the File System Access API. Currently only Chromium-based browsers like Chrome and Edge support it. Other browsers like Firefox and Safari don't support it, so in that case Construct falls back to showing other alternatives.

  • Construct's preview window doesn't get any special treatment: it's still subject to the usual autoplay restrictions.

    What might make this confusing though is IIRC Chrome tracks statistics about how often media playback is used on different websites, and may decide to allow autoplay automatically based on usage patterns. In other words if you usually play audio on some page, then it will start allowing autoplay. So you might get autoplay allowed in the preview window if you usually play audio in preview. In the end that could create the impression that autoplay works inconsistently, as it ends up working for some people but not others.

  • When you enable worker mode your scripts run in a web worker, which don't have direct access to window and associated events. (Keyboard input can still be detected via runtime events, but you can't prevent default on them, because the event already finished on the main thread.) If you try to use window in a worker, it will throw errors which should appear in the browser console.

    Worker mode "auto" will default to using a worker, unless you add scripts to your project, in which case it turns off worker mode. This is because people tend to write scripts that access things like window and document, so the default is to allow that to work. This is noted in the manual here.

  • In order to make well-designed software, it's important to know how and why people do things with it. That's all I'm trying to do here: establish why this is really a problem, understand the situation so it can be best addressed, and then come up with the best way to solve it.

    One of the reasons I'm somewhat surprised by this particular point about X buttons in tabs is there are lots of places in the UI where different clickable options are close to each other: context menus, properties, toolbar buttons, lists of actions, and so on. Aren't those a problem too?

    Perhaps it's just that it's annoying to recover from an accidental click due to the issue with moving tabs. Solving that might mean that there isn't actually such a need to remove the X button. This type of thing is why I'm trying to understand the problem better, rather than just jumping to conclusions and adding workarounds (which as Diego alluded to tend to compound over time, cause bugs, and end in poorly designed software). This is our approach to every aspect of Construct - if someone insists on a change without explanation, it's unlikely we'll act on it, especially as we are always very busy with a huge pile of other things we know really are important. This is also why we have our feature request and bug report systems: they're intended to help make all of this clear so we can actually act on what you want.

  • Even with a short tab name like "Layout 1", there is a much bigger area to click on the tab to select it than to close it. The X is pretty small and so should actually be difficult to click - like the famously tiny small X button on ads that people complain about being hard to close. How is it possible to repeatedly accidentally click a small button? I don't understand this at all, can someone explain?

  • Browsers restrict audio playback until the user interacts with the page, in order to prevent random web pages annoying you with audio ads and such.

    You can play audio in 'Start of layout', but it won't actually be heard until the first click or touch on the page.

    There's more information in the "Autoplay restrictions" section of the Audio manual page.

  • nothing happens when browser invoke download is triggered

    See the warning by 'Invoke download' in the manual. It only works in actual browsers.

    Downloading is a browser feature and depends on the browser UI. Note that mobile apps don't run in browsers (there is no address bar etc), so the download feature isn't available there. Consider using the Share plugin to share the file instead.

  • By "next beta cycle" I mean "the first beta release after the next stable release". We aim to minimise changes in the run-up to a stable release to ensure a smooth release.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I have another issue with transparency and 3D Objects, but only when I use the "Fog" effect.

    This is a different issue to the one originally discussed in this thread. It's covered in the tutorial Using 3D in Construct under "Transparency and fog", and in the latest beta the "Foggy outbreak" project has been updated to work correctly.

  • Chromium-based browsers like Chrome and Edge support saving to a folder. Currently Firefox and Safari don't support it yet.

    I'd strongly recommend just using the browser - the NW.js editor builds are basically deprecated, no longer developed, probably have a bunch of bugs that don't happen in the browser, and providing you use a Chromium-based browser no longer does anything much that browsers can't do now.

  • You shouldn't need to simulate mouse input to do this. You can make clicking an object call a function, and then call the function instead of simulating input, to do the same thing as if the object was clicked.

  • See Icons & Splash in the manual - specifically the splash part, as that's the first thing shown when the app starts.

  • Are you sure that's what you want? It will reload the page and so restart the project. Only the hash can be changed without reloading.

  • Windows Phone was discontinued years ago, so not much point trying to publish for that... but you can still package up web exports and list them in the Microsoft Store with PWABuilder.

  • Advanced Minify renames pretty much everything in the JavaScript code. However providing you follow the manual guide on writing code for advanced minification, it won't change how it runs at all, which usually means you don't have to worry about exactly what it renames.