Ashley's Recent Forum Activity

  • Try using PWABuilder.

  • You can directly import fonts to Construct, and then use them in the built-in Text object. I'd recommend using WOFF format fonts though for full compatibility across browsers and platforms.

    If you want to share the project files, then try using shared folders in Google Drive and Microsoft OneDrive with Construct's cloud save. For example you could set up a shared folder that all students can save their project to. There's more information in the manual entry on sharing projects.

  • I don't know, I've never really worked with or tested CSS filters with Construct, as everything normally happens in WebGL rendering. In general applying things like this may not work well, as Construct does not know about them, so they could conflict with things Construct is trying to do.

  • I'd recommend using a layout effect, as it works within the Construct engine and so Construct can ensure it's handled efficiently and appropriately. For example if you use "low quality" fullscreen mode, a layout effect will process efficiently at low-resolution and then stretch the result up to the display; but with a CSS filter the browser doesn't know anything about how the content got rendered, so all it can do is process the effect on the full-resolution canvas, which is less efficient. Also while I'm not clear of all the details, effects run by Construct are very likely to be GPU-accelerated, but there's a chance some browsers in some cases might drop CSS filters back to software rendering and so exhibit poor performance.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • It has less features worse performance... but I think it wins in graphics...

    Construct has some very advanced graphics capabilities, including the ability to stack multiple effects on objects, layers and layouts, as well as the new sub-layers feature which allows for some much more advanced and more efficient visual effects.

    I wish however we had an easyer way of implementing scrolling backgrounds on Construct 3 ...

    This shouldn't be too difficult - the endless runner example shows one way of doing it. It can also be done by changing the image offset.

  • "Letterbox integer scale" constrains the available sizes quite a lot. If it's suitable for the art style, try just "letterbox scale".

    Other than that try using the Browser object's 'Request fullscreen' action, although IIRC it's not supported on iOS.

  • By default the runtime is hosted in a Web Worker, where there is no direct access to the DOM (window, document etc.) You can force the project to run in the DOM by setting 'Use worker' to 'No' in project properties, and this will allow such calls to work again.

    However addons can support this in a web worker using a specially designed DOM call mechanism in the runtime. This is documented in the addon SDK manual.

    Global variables are not exposed in the SDK. This is because a well-designed addon should not hard code such things. It should just make the information available, e.g. via an expression, and then the user can assign that to a global variable in the event system.

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

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,430,924 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
  • x108
    Coach One of your tutorials has over 1,000 readers
  • x62
    Educator One of your tutorials has over 10,000 readers
  • x3
    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
  • x36
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs