Age | Commit message (Collapse) | Author |
|
(cherry picked from commit e13bcf5b845fba1dbb2bbb02c8f14e7d3733a188)
|
|
Fold resources when non-main inspector exits tree
|
|
|
|
Fixes #73192.
|
|
|
|
|
|
|
|
|
|
|
|
Allow AnimationStateMachine / AnimationNode to restart when transitioning to the same state
|
|
|
|
Remove set_drag_forwarding_compat()
|
|
Fix recursive resource inclusion check
|
|
|
|
Implement export_multiline support for Array[String] and Dictionary
|
|
I forgot a line of code.
Fixes #71194.
|
|
* This solution is much cleaner than the one in 3.x thanks to the use of callables.
* Works without issues in any language (no need to worry about camel or snake case).
* Editor code uses a compatibility function (too much work to redo).
Fixes #59899
|
|
* Remove unused `EditorPropertyMember` and related hints, previouly used by
VisualScript. Such logic should be implemented in the VS module itself.
* As the above broke compatibility with the VS module, clean up the other
hacks that were still in core in support of VisualScript.
* `PROPERTY_USAGE_INTERNATIONALIZED` was only used in Object's
`get_translatable_strings()`, which is a legacy function not used anywhere.
So both are removed.
* Reordered some usage flags after the above removal to minimize the diff.
* General clean up.
Fixes #30203.
Co-authored-by: Rémi Verschelde <rverschelde@gmail.com>
|
|
Use BitField<> in core type masks
|
|
* All core types masks are now correctly marked as bitfields.
* The enum hacks in MouseButtonMask and many other types are gone. This ensures that binders to other languages non C++ can actually implement type safe bitmasks.
* Most bitmask operations replaced by functions in BitField<>
* Key is still a problem because its enum and mask at the same time. While it kind of works in C++, this most likely can't be implemented safely in other languages and will have to be changed at some point. Mostly left as-is.
* Documentation and API dump updated to reflect bitfields in core types.
|
|
Fixes #43177
|
|
|
|
As many open source projects have started doing it, we're removing the
current year from the copyright notice, so that we don't need to bump
it every year.
It seems like only the first year of publication is technically
relevant for copyright notices, and even that seems to be something
that many companies stopped listing altogether (in a version controlled
codebase, the commits are a much better source of date of publication
than a hardcoded copyright statement).
We also now list Godot Engine contributors first as we're collectively
the current maintainers of the project, and we clarify that the
"exclusive" copyright of the co-founders covers the timespan before
opensourcing (their further contributions are included as part of Godot
Engine contributors).
Also fixed "cf." Frenchism - it's meant as "refer to / see".
|
|
This reverts commit c774b4ce1777d19789bec1cbef100f26c6927777, reversing
changes made to ccc609d824802d1d1a20f34bda69ecac75f5a8a1.
|
|
Toggling the keying state does not significantly change the structure
of the inspector. So it's ok to propagate the keying state and then
use `queue_redraw()` to update the keying icon.
|
|
For arrays, specifically check if it's a string array and pass the
type on to the editor. For dictionaries, save the hint on the type and
use it later to draw the multiline editor, except for when adding a
string key, because that doesn't make much sense. All string values
however will be drawn as multiline.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Unify usage of undo_redo in editor
|
|
|
|
|
|
Unify usage of GLOBAL/EDITOR_GET
|
|
Added custom node export
|
|
|
|
|
|
|
|
|
|
|
|
change warnings=all to use /W4.
|
|
Fix `hide_slider` vs `no_slider` inconsistency in editor property code
|
|
|
|
|
|
Rindbee/fix-property-link-not-work-in-MultiNodeEdit
Set the changed field to empty (meaning all) if the link button is pressed
|
|
"less" should be used for quantity, rather than "lesser".
Existing scripts that use `or_lesser` in `_get_property_list()`
will need to be updated to account for this change.
|
|
Improve null and object printing to avoid confusion with arrays
|
|
- Use different syntax for object printing to avoid confusion with arrays.
- Print null as `<null>` to avoid confusion with a string `"null"`.
- Display `<empty>` in editor resource pickers to avoid confusion
with array-based properties.
|