| Age | Commit message (Collapse) | Author |
|---|
|
jsdoc has no new release so I'm tracking this PR:
https://github.com/jsdoc/jsdoc/pull/1906
|
|
(cherry picked from commit d1f023c35b8bed3fc839fdc5d587a839568aab44)
|
|
Some Vulkan debugging prints were also changed to be printed only
in verbose mode.
|
|
[HTML5] Fix target_fps when window loses focus.
|
|
We don't get updates when the window is unfocused/minimized, so we must
detect the situation where the counted ticks start drifting away
resulting in more frames drawn than needed.
This commit adds a check to ensure that the target ticks do not drift
away more than one second.
|
|
See discussion in #43811, it was only implemented on iOS and even that
implementation was fairly limited. This would best be provided as plugins
for Android and iOS without cluttering the shared OS API.
|
|
For consistency with the native one, and the documentation.
|
|
|
|
Port changes to the "raycast" module build files from 3.x
|
|
|
|
|
|
[iOS] Nonnegative start index for virtual keyboard range
|
|
|
|
Library suffix should be `.a`, the `EXTRA_` in
`EXTRA_EXPORTED_RUNTIME_METHODS` is deprecated.
|
|
Follow-up to #38736 (these uses were likely added after this PR was merged).
|
|
|
|
Core: Drop custom `copymem`/`zeromem` defines
|
|
Android: Upgrade buildTools from 30.0.1 to 30.0.3
|
|
We've been using standard C library functions `memcpy`/`memset` for these since
2016 with 67f65f66391327b2967a20a89c3627e1dd6e84eb.
There was still the possibility for third-party platform ports to override the
definitions with a custom header, but this doesn't seem useful anymore.
|
|
[HTML5] Export as Progressive Web App
|
|
Adds possibility to export as a progressive web app.
Allows customizing base icons, display mode, orientation and offline
page.
|
|
Linux: Remove use_static_cpp override on x86_32
|
|
Generates a key/cert snakeoil pair or use a custom SSL cert/key.
This is of course false security, and potentially detrimental for it.
But, so long, those are the requirements browser vendors agreed on to
use things like the Gamepad API, and more advanced topics like wasm
threads.
You don't need this if you run on localhost (at least!), but you do
need this (or a much safer nginx proxy) to try those things on your
local network (e.g. when debugging a phone, networking, etc).
|
|
We used to only generate the favicon if it was specified in the user
project settings, now it's optional, will export it to `NAME.icon.png`,
(falling back to the default project icon if none is set in project
settings), and the `<link>` tag is added using the `$HEAD_INCLUDE`
instead of being hardcoded in the template.
|
|
Serving all files in that folder and using a known list of mime types.
Makes it easy to add more exported files, while still playing safe.
|
|
directly by the plugin.
|
|
It seems 30.0.1 had issues with compatibility with JDK 8 and 11,
which appear to be solved in 30.0.3 as per godotengine/godot-docs#4796.
|
|
After further testing it seems to work fine now when building binaries with GCC 5
on Ubuntu 16.04 (previously we were using GCC 9 on Ubuntu 14.04).
Follow-up to #45629.
|
|
Follow-up to #46810, this was missed in #47079 when fixing the issue
for other platforms.
Fixes #48135.
|
|
Re-add "no-exceptions" for export templates builds with ICU.
|
|
Validation layers on Android
|
|
|
|
SilverCreekEntertainment/add-uwp-export-project-notifier
Fix EditorExportPlugin _export_begin and _export_end functions not being called when exporting UWP
|
|
|
|
|
|
APK" error and improve command output logging.
|
|
|
|
called when exporting UWP
in uwp's version of export.cpp create a ExportNotifier object so that EditorExportPlugin _export_begin and _export_end functions will be called as documentated.
|
|
|
|
|
|
Add support for forwarding callbacks from Godot's parent activity
|
|
|
|
|
|
|
|
`requestCode` and deprecate support for forwarding callbacks from Godot's parent activity.
|
|
According to project settings and when WebGL2 is not available.
This does nothing in current master, as we have no rendering yet!
|
|
|
|
|
|
We were using `Content-Length` from the server when `Content-Encoding`
was not set (i.e. response was not compressed).
Sadly, in CORS requests accessing headers is restricted, and while
`Content-Length` is enabled by default, `Content-Encoding` is not.
This results in the impossibility of knowing if the content was
compressed, unless the server explicitly enabled the encoding header
via `Access-Control-Expose-Headers`.
To keep maximum compatibility we must disable `body_size` completely.
|
|
|