Age | Commit message (Collapse) | Author |
|
Change all WEBP strings and comments to WebP
|
|
Make creating window do not flicker when specify custom position
|
|
|
|
Add Selection and Caret for Next Occurrence of Selection
|
|
|
|
|
|
Adds the bind `add_selection_for_next_occurrence` to TextEdit, with CTRL+D as the default shortcut.
When the bind is performed, ff a selection is currently active with the last caret in text fields, searches for the next occurrence of the selection, adds a caret and selects the next occurrence.
If no selection is currently active with the last caret in text fields, selects the word currently under the caret.
The action can be performed sequentially for all occurrences of the selection of the last caret and for all existing carets. The viewport is adjusted to the latest newly added caret.
The bind and the behaviour is similar to VS Code's "Add Selection to Next Find Match" and JetBrains' "Add Selection for Next Occurrence". It takes advantage of the multi-caret API.
The default shortcut for `select_word_under_caret` has been changed to ALT+G, in order to give priority to CTRL+D for `add_selection_for_next_occurrence` to better align with popular IDEs and editors.
|
|
Fix big negative numbers printing incorrect decimals in `num_real`
|
|
|
|
|
|
|
|
Make String.simplify_path keep the protocol identifier for urls
|
|
|
|
|
|
Add `is_finite` method for checking built-in types
|
|
Fix inserting tabs in TextEdit
|
|
|
|
|
|
|
|
|
|
This also removes `OS::can_use_threads` from the public API since it's always
true.
|
|
Delete `set_all`, `set_axis`, and `get_axis` methods from Vector2/3/3i/4/4i
|
|
Improve string formatting (%f and %v) for inf and nan
|
|
Using codespell 2.3-dev from current git.
And fix typo in `methods.py` for `vsproj=yes` option (still won't work
though).
|
|
add macros to generate wrappers for module functions.
|
|
Use double instead of real_t type for time-related parameters and variables
|
|
Addresses #65313
|
|
|
|
|
|
|
|
|
|
Removes separate `Command` key (use `Meta` instead).
Adds an event flag to automatically remap `Command` <-> `Control` (cannot be set alongside `Control` or `Meta`).
|
|
This exposes PhysicsServer2DManager and PhysicsServer3DManager.
|
|
Rename every instance of `caret_blink_speed` to `caret_blink_interval`
|
|
It's been changed in EditorSettings, LineEdit, TextEdit.
Affects setters and getters, and passed parameters, too.
|
|
|
|
Also replace has_no_surface with has_surface
|
|
|
|
|
|
Co-authored-by: Resul Çelik <resul_celik@hotmail.com>
|
|
|
|
|
|
|
|
gutter by calling TextEdit::_update_gutter_width in TextEdit::add_gutter & TextEdit::remove_gutter
Update TextEdit gutters subcase, gutter add and remove to ensure gutter total width is correct
Fix test_code_edit symbol lookup test case to include padding (+2)
|
|
"sampling" is a more accurate term than "interpolating" for what's
happening when using that function.
|
|
Also fix:
- Geometry3D::get_closest_distance_between_segments() returning
incorrect values.
- Test for Geometry3D::get_closest_distance_between_segments() testing for
an incorrect value.
|
|
|
|
|
|
|
|
NOTIFICATION_THEME_CHANGED"
This reverts commit 4b817a565cab8af648c88cfc7ab6481e86ee3625.
Fixes #64988.
Fixes #64997.
This caused several regressions (#64988, #64997,
https://github.com/godotengine/godot/issues/64997#issuecomment-1229970605)
which point at a flaw in the current logic:
- `Control::NOTIFICATION_ENTER_TREE` triggers a *deferred* notification with
`NOTIFCATION_THEME_CHANGED` as introduced in #62845.
- Some classes use their `THEME_CHANGED` to cache theme items in
member variables (e.g. `style_normal`, etc.), and use those member
variables in `ENTER_TREE`, `READY`, `DRAW`, etc. Since the `THEME_CHANGE`
notification is now deferred, they end up accessing invalid state and this
can lead to not applying theme properly (e.g. for EditorHelp) or crashing
(e.g. for EditorLog or CodeEdit).
So we need to go back to the drawing board and see if `THEME_CHANGED` can be
called earlier so that the previous logic still works?
Or can we refactor all engine code to make sure that:
- `ENTER_TREE` and similar do not depend on theme properties cached in member
variables.
- Or `THEME_CHANGE` does trigger a general UI update to make sure that any
bad theme handling in `ENTER_TREE` and co. gets fixed when `THEME_CHANGE`
does arrive for the first time. But that means having a temporary invalid
(and possibly still crashing) state, and doing some computations twice
which might be heavy (e.g. `EditorHelp::_update_doc()`).
|