Age | Commit message (Collapse) | Author |
|
Pass by reference to const
|
|
|
|
This results in slightly smaller binaries (-17 KB for an editor binary)
as no strings need to be allocated.
|
|
Fixes minor issues found by static analyzer
|
|
|
|
|
|
Particles / CPUParticles: Return uniform density spheres.
|
|
Added DEPTH_TEXTURE to visual shaders
|
|
This matches the previous change for cpu_particles.
|
|
For clarity, assign-to-release idiom for PoolVector::Read/Write
replaced with a function call.
Existing uses replaced (or removed if already handled by scope)
|
|
|
|
Remove unused icons in the default theme
|
|
|
|
|
|
Add a Direction property to ParticlesMaterial
|
|
Fix some editor crashes
|
|
|
|
Applied some of FALLTHROUGH macro usage from #30122
|
|
compiler that this is intended.
|
|
Add default values to the editor help, docs, and generated RST
|
|
Also, make spacing of "=" in the editor help a bit more consistent.
Closes #16086
|
|
Shows menu when dragging connection on empty space in visual shader
|
|
|
|
Remove redundant code, possible NULL pointers and others
|
|
|
|
|
|
Give LineEdit/TextEdit a custom color for font while uneditable
|
|
Previously there was some transparency hard coded into TextEdit when in read only mode.
This change adds a custom color for adjusting the font in read only mode.
It also applies when syntax highlighting is on.
|
|
By default the LineEdit's text when editable is unchecked had some transparency hardcoded.
This change adds a custom color to LineEdit for adjusting the font when editable is off.
Addresses issue 29814
|
|
Set to enum variables, only correct values
|
|
|
|
Fix expression node crashes
|
|
Partial revert of 02319dceb2e17184eb765c67719a306f56dafc1b,
previous code handled this cases without errors and the TileSet and
TileSetEditorPlugin are written with the expectation that those will
not error out.
This is a bit wonky and these classes should likely be refactored,
but until then it's best to keep things as they were.
Fixes #29962.
|
|
|
|
The setters are called when the property is first initialized, and before
that its default min and max are 0.0 and 1.0 respectively.
If you configured min_value to 1.0 and max_value to e.g. 3.0, since the
min_value setter can be called before that of max_value (which thus still
defaults to 1.0), the min will be set to 0.99.
Same conflict could happen with a configured max_value of 0 if its setter
is called before that of a valid, negative min value.
|
|
Right now it would take garbage values when loading scenes,
which could end up written to the scene file.
|
|
|
|
Remove always true/false values
|
|
|
|
Tweak SpatialMaterial's default metallic and roughness texture channels
|
|
|
|
Added ERR_FAIL checks for `Animation::track_set_key_value` and `AnimationNodeStateMachine::remove_node`
|
|
|
|
ResourceFormatLoader and ResourceFormatSaver are meant to be overridden
to add support for different formats in ResourceLoader and ResourceSaver.
Those should be exposed as they can be overridden in plugins.
On the other hand, all predefined subclasses of those two base classes
are only meant to register support for new file and resource types, but
should not and cannot be used directly from script, so they should not
be exposed.
Also unexposed ResourceImporterOGGVorbis (and thus its base class
ResourceImporter) which are editor-only.
|
|
This is only meant to check the validity of the whole codebase every
now and then, or to apply clang-format config changes when relevant.
|
|
This partially addresses #19242.
|
|
This is a new singleton where camera sources such as webcams or cameras on a mobile phone can register themselves with the Server.
Other parts of Godot can interact with this to obtain images from the camera as textures.
This work includes additions to the Visual Server to use this functionality to present the camera image in the background. This is specifically targetted at AR applications.
|
|
Add toggle for hidden file visibility in FileDialog
|
|
It's not necessary, but the vast majority of calls of error macros
do have an ending semicolon, so it's best to be consistent.
Most WARN_DEPRECATED calls did *not* have a semicolon, but there's
no reason for them to be treated differently.
|
|
|