Age | Commit message (Collapse) | Author |
|
|
|
Improves VideoPlayer's documentation
|
|
Fix iOS Crash on Application Exit
|
|
doc: Mention the limited comment support in ConfigFile
|
|
|
|
|
|
HTML5 callbacks rework.
|
|
Fix minimap updating in shader tab
|
|
|
|
Added missing form of array constructor in shaders
|
|
|
|
|
|
Improved MenuButton Description
|
|
I expanded description of MenueButton to explain how to create the items inside of the pop up as this is initially a mystery to many new people.
|
|
Fixes compatibility with emscripten 1.39.5+ .
Most input callbacks now require a target and no longer support NULL
defaults.
This commit changes all required null targets to the expected default in
the binding phase.
Since for canvas-related callbacks there is no default, the "#canvas"
selector is used instead.
Additionally, since canvasX and canvasY event properties are no longer
supported, event positions are computed from "clientX" and "clientY" and
the "#canvas" bounding client rect.
|
|
Android: Improve name of icon export properties
|
|
Mark alternate editor display modes as disabled in the GLES2 renderer
|
|
This partially addresses #27018.
|
|
Fix crash when confirming dialogs with Return key
|
|
HTML5: Address removal of 'timestamp' in Emscripten 1.39.5
|
|
It was removed as noted in the changelog:
https://github.com/emscripten-core/emscripten/blob/1.39.5/ChangeLog.md#v1395-12202019
> Removed `timestamp` field from mouse, wheel, devicemotion and
> deviceorientation events. The presence of a `timestamp` on these
> events was slightly arbitrary, and populating this field caused
> a small profileable overhead that all users might not care about.
> It is easy to get a timestamp of an event by calling
> `emscripten_get_now()` or `emscripten_performance_now()` inside
> the event handler function of any event.
Fixes #34648.
|
|
This seems more readable and still includes the required dimensions.
|
|
Regression from #34040, apparently making this a const reference
introduces issues (not sure why, but previous code worked fine).
Fixes #34691.
Co-authored-by: dankan1890 <mewuidev2@gmail.com>
|
|
lakshay-angrish/35090-methods-in-xml-not-in-editor
show parametric setters and getters in editor help
|
|
|
|
Improves LineEdit documentation
|
|
ChibiDenDen/constant_lookup_through_subclass_instance
Fix constant access in base class through subclass instance
|
|
* Recently supported macOS shortcuts are added
* Makes it clear than `set_text` won't trigger `text_changed`
* `minimum_spaces` is the number of space characters that can be shown
without scrolling
|
|
|
|
|
|
'I guess there is no one to (git) blame
We're leaving ground...
Will things ever be the same again?'
|
|
New contributor added to AUTHORS:
@dankan1890
Thanks to all contributors and donors for making Godot possible!
|
|
Fixes as issue where a subclass calls a base class method that tries to access a constant from the script.
The original code went through every ower class, and for each owner, went through its inheritance tree.
This seems like the wrong order, the modified code goes to each base class, and for each base class goes through the owner tree.
This is more in line with what the parser does, as the current impelemtation allows an access that the parser does not support.
This change should not negatively affect existing code due to the way the parser works
|
|
ENet optional server_relay when disconnecting peer
|
|
Fix issue regarding rotating Canvas Items in editor
|
|
Add multimesh format max for proper error checking
|
|
refresh area2d collision when shape changes
|
|
Fix errors raised when showing parse errors in the editor
|
|
|
|
Fix SkeletonIK not playing animation if more than one IK-Bone is active
|
|
Gracefully handle 3D textures in GLES2
|
|
Mono/C#: Script interface calls now attach the current thread
|
|
Update libwebp to 1.1.0
|
|
Fixes #26691
|
|
|
|
|
|
|
|
Fix error exporting to X11 with embedded PCK
|
|
Fixes #32513.
|
|
Added guards to all C# script interface calls to attach the current thread
for the current scope if the thread is not already attached.
This is far from ideal, as attaching the thread is not cheap and all managed
thread local storage is lost when we detach the thread at the end of the calls.
However, it's the best we can do for now to avoid crashing
when an unattached thread tries to interact with C# code.
|