Age | Commit message (Collapse) | Author |
|
Rename `window_get_real_size`, add position counterpart.
|
|
`window_get_position_with_decorations`.
|
|
DisplayServer::screen_is_touchscreen will likely never utilize its
parameter p_screen.
This PR replaces this function by DisplayServer::is_touchscreen_available()
with the same functionality.
This solves the problem, that a SubViewport was used for determining
the screen, which resulted in error messages.
|
|
Clean up DisplayServerAndroid::window_get_native_handle() with the GLES3 renderer
|
|
renderer
|
|
Add support for font weight and stretch selection when using system fonts.
Add function to get system fallback font from a font name, style, text, and language code.
Implement system font support for Android.
Use system fonts as a last resort fallback.
|
|
|
|
Add necessary build flags and switch from using a
GLES2 context to a GLES3 one.
This also enables building for OpenXR
Co-authored-by: m4gr3d <fhuyakou@gmail.com>
Co-authored-by: dsnopek <dsnopek@gmail.com>
|
|
Improves the base functionality for the Android platform and helps reduce the amount of spurious error logs emitted.
|
|
We would needlessly get file names like `*.arm64.armv8.o`.
|
|
|
|
Boolean stringification changed in Godot 4.0.
Fixes #67034.
Co-authored-by: Hugo Locurcio <hugo.locurcio@hugo.pro>
|
|
|
|
Remove redundant non-trivial Variant types initializations
|
|
- Ensure all strings with ellipsis end with 3 periods instead of 2.
- Fix extraneous period in "Error calling from signal '...' to callable"
messages.
|
|
|
|
|
|
|
|
[Android] Fix GDExtension export and loading.
|
|
|
|
|
|
Fixes the wrong mapping of `Key::HOME`. Androids `KEYCODE_HOME` is in fact the hardware home button the right mapping is `KEYCODE_MOVE_HOME`.
Also adds mappings to keys that were not present before.
|
|
Fix build with Vulkan disabled and no Vulkan headers installed.
|
|
Unify usage of GLOBAL/EDITOR_GET
|
|
Use proper types for converting Java float/double arrays in Android code
|
|
Make creating window do not flicker when specify custom position
|
|
|
|
|
|
This provides parity with the `InputEventMouseButton` allowing for proper conversion between the two events.
|
|
Update the `clean` task configuration: running `gradlew clean` will now properly delete the generated build artifacts
|
|
|
|
|
|
Optimize Android export process
|
|
|
|
|
|
|
|
|
|
Replace all TODO uses of `#warning` by proper TODO comments, and will open
matching bug reports to keep track of them.
We don't have a great track record fixing TODOs, but I'd wager we're even
worse for fixing these "TODO #warning" so we should prohibit this usage.
|
|
|
|
Cleanup of the Android cursor shape logic
|
|
|
|
Fix null in android keyboard handling.
|
|
|
|
https://github.com/godotengine/godot/pull/66242
|
|
Enhance portability of threading
|
|
|
|
akien-mga/core-unix-remove-NO_FCNTL-and-NO_STATVFS
Unix: Remove now unnecessary I/O defines, cleanup
|
|
- `LIBC_FILEIO_ENABLED` wasn't defined anywhere, even in _other platforms_.
- `NO_NETWORK` is also never defined. It probably isn't enough anyway to
disable network APIs in the current codebase.
- `UNIX_SOCKET_UNAVAILABLE` is never defined in this code but used by some
other platforms, clarify that.
- `NO_STATVFS` can be removed as Android supports it since API level 19,
which is our current min SDK level. It's also only used for
`DirAccessUnix::get_space_left()` which is anyway overridden by
`DirAccessJAndroid::get_space_left()` so it shouldn't make a difference.
* Fixed documentation for `DirAccess.get_space_left()`.
- `NO_FCNTL` is likely also a remnant of early Android days, in current NDK
r23 it seems to be available. Also cleaned up unused `fcntl.h` includes.
- `NO_ALLOCA` is never defined, and we use alloca in many places now.
|
|
Android was the last platform to still attempt to disable RTTI (for binary
size), but both the Android editor and now the ICU library used by templates
need RTTI.
There could still be the possibility to support this for non-ICU template
builds (i.e. without the TextServerAdvanced module), but since this isn't one
of the build configurations we test regularly it's pretty risky to keep this
option only for that specific use case. And our code is already littered with
`dynamic_cast`s which weren't guarded with `!defined(NO_SAFE_CAST)`.
|
|
|