| Age | Commit message (Collapse) | Author |
|---|
|
Alignment of scene pixels on screen pixel ensure a crisp rendering of small features (such as text). Unfortunately, alignment of top left pixel on screen adds a lot of jittering when zooming at high zoom factor.
This change allow to snap the top left scene pixel on the closest screen pixel (not only the top-left most), and we do so only when the scale factor is an integer.
|
|
For us, it practically only changes the fact that `A<A<int>>` is now
used instead of the C++03 compatible `A<A<int> >`.
Note: clang-format 10+ changed the `Standard` arguments to fully
specified `c++11`, `c++14`, etc. versions, but we can't use `c++17`
now if we want to preserve compatibility with clang-format 8 and 9.
`Cpp11` is still supported as deprecated alias for `Latest`.
|
|
Update all editor viewports after settings changes
|
|
|
|
Removed underlining of not clickable symbols
|
|
|
|
The AABB for an empty Spatial has 0 size, since the stored and
compared Transform was scaled by the AABB size, it would completely
destroy the rotation information. If there is no rotation
information, the gizmo doesn't update when the rotation changes.
|
|
Made snap relative work on rotation as well
|
|
The line to update the option was missing (rendering it useless).
Of course the only one I didn't know how to test was broken.
|
|
ScriptDebugger refactor, threading, profilers.
|
|
|
|
Update snap setting only with OK
|
|
Fix the VIEW_INFORMATION checkbox not being selected (visually)
|
|
Move Debug menu logic to DebuggerEditorPlugin, allow 4 debug instances
|
|
|
|
|
|
|
|
restore previous values with cancel
|
|
Generated id of "Display Advanced..." was in conflict with "View Information"
|
|
|
|
This was done by mistake in #36758, but it's not necessary and actual
causes a bug.
`property_changed` is only emitted via `emit_changed()`, which already
has default values for `p_field` and `p_changing`.
Also reverted to using `String` for now to be on the safe side, even if
it's inconsistent with `emit_changed()`. I had only changed it
partially in #36758 so it was inconsistent. It probably does make sense
to port `EditorInspector` and related property editors to use
`StringName` where relevant, but that's for a dedicated PR.
Fixes #36799.
|
|
Improve the GIProbe editor contextual label
|
|
- Fix `callable_mp` bindings to methods which used to have default
arguments passed to `bind_method`. We now have to re-specify them
manually when connecting.
- Re-add `GroupsEditor::update_tree` binding.
- Misc code quality changes along the way.
|
|
- Change the label color depending on the estimated performance
(green = fast, yellow = average, red = slow).
- Use the Unicode multiplication symbol.
- Make the label translatable.
|
|
Fix non-latin layout scancodes on Linux, adds access to physical scancodes.
|
|
Partial revert "Fix two signal errors"
|
|
|
|
It's tedious work...
Some can't be ported as they depend on private or protected methods
of different classes, which is not supported by callable_mp (even if
it's a class inherited by the current one).
|
|
Remove now unnecessary bindings of signal callbacks in the public API.
There might be some false positives that need rebinding if they were
meant to be public.
No regular expressions were harmed in the making of this commit.
(Nah, just kidding.)
|
|
Rename Navigation{Mesh,Polygon}Instance and PlaneShape for clarity
|
|
|
|
Add a soft line length guideline to the script editor
|
|
Mention version compatibility when there are no results in the assetlib
|
|
Decrease the script editor's default split width to 70
|
|
|
|
Fix autocomplete and highlighting for new integer types
|
|
+ renamed _on_nodes_delete to _delete_nodes
|
|
|
|
Types include new integer types and others
|
|
|
|
|
|
|
|
|
|
- Renames PackedIntArray to PackedInt32Array.
- Renames PackedFloatArray to PackedFloat32Array.
- Adds PackedInt64Array and PackedFloat64Array.
- Renames Variant::REAL to Variant::FLOAT for consistency.
Packed arrays are for storing large amount of data and creating stuff like
meshes, buffers. textures, etc. Forcing them to be 64 is a huge waste of
memory. That said, many users requested the ability to have 64 bits packed
arrays for their games, so this is just an optional added type.
For Variant, the float datatype is always 64 bits, and exposed as `float`.
We still have `real_t` which is the datatype that can change from 32 to 64
bits depending on a compile flag (not entirely working right now, but that's
the idea). It affects math related datatypes and code only.
Neither Variant nor PackedArray make use of real_t, which is only intended
for math precision, so the term is removed from there to keep only float.
|
|
Add `physical_keycode` (keyboard layout independent keycodes) to InputEventKey and InputMap.
Fix non-latin keyboard layout keycodes on Linux/X11 (fallback to physical keycodes).
|
|
These bugs existed since those lines were added, so I assume that
their intended use is no longer relevant.
|
|
This closes #36469.
|
|
This partially reverts commit a31bc1b0ba608ef340068676f6709621a37f2140.
Possible compatibility issues with #35864 that I am not sure about.
Do I need to change "connect" to "connect_compat"?
|
|
This attribute is now part of the standard we target so we no longer
need compiler-specific hacks.
Also enables -Wimplicit-fallthrough for Clang now that we can properly
support it. It's already on by default for GCC's -Wextra.
Fixes new warnings raised by Clang's -Wimplicit-fallthrough.
|
|
Refactor node processing in visual shader member dialog
|