| Age | Commit message (Collapse) | Author |
|---|
|
System for GDScript warnings
|
|
- Count and panel per script.
- Ability to disable warnings per script using special comments.
- Ability to disable warnings globally using Project Settings.
- Option to treat enabled warnings as errors.
|
|
Closes #19140
|
|
|
|
added get_creation_time function for gdscript
|
|
Allow some non-integer built-in constants in gdscript
|
|
Fix SortArray crashing with bad comparison functions
|
|
|
|
|
|
-Added expression evaluation to EditorSpinSlider, fixes #20813, fixes #18932
|
|
|
|
Fix #20564 HDR import fail
|
|
|
|
Fix nested Vectors
|
|
|
|
|
|
|
|
Token has extra "0" at the end so it fail condition checking.
|
|
|
|
likely many others
|
|
When a Vector of Vectors gets resized the 'this' pointer of the Vectors
change. This means that the VectorWriteProxy _parent references get
invalidated. Thanks a lot to @ibrahn for finding the root cause of this.
To fix this we now create a pointer to CowData in Vector (which won't
change when the vectors move) and pass that to the write proxy also.
This fixes #20475
|
|
Yesterday, when playing around with my network code, I realized there is
a security issue in decode_variant, at least when decoding PoolArrays.
Basically, the size of the PoolArray is encoded in a uint32_t, when
decoding it, that value is cast to int when comparing if the packet is
actually that size causing numbers with MSB=1 to be interpreted as
negative thus always passing the check. That same value though, is used
as uint32_t again to resize the output vector. For this reason, sending
a malformed packet with declared type PoolByteArray and size of 2^31(+x)
causes the engine to try to allocate 2+GB of pool memory, causing the
engine to crash.
(cherry picked from commit 5262d1bbcc81a06db66ac45c3f75535f231268bc)
|
|
fixes NameError (missing "subprocess_main" and "basestring")
|
|
Add "editor" and "standalone" feature tags
|
|
Fixed shortcuts not working with InputEventActions
|
|
- Refactored all builder (make_*) functions into separate Python modules along to the build tree
- Introduced utility function to wrap all invocations on Windows, but does not change it elsewhere
- Introduced stub to use the builders module as a stand alone script and invoke a selected function
There is a problem with file handles related to writing generated content (*.gen.h and *.gen.cpp)
on Windows, which randomly causes a SHARING VIOLATION error to the compiler resulting in flaky
builds. Running all such content generators in a new subprocess instead of directly inside the
build script works around the issue.
Yes, I tried the multiprocessing module. It did not work due to conflict with SCons on cPickle.
Suggested workaround did not fully work either.
Using the run_in_subprocess wrapper on osx and x11 platforms as well for consistency. In case of
running a cross-compilation on Windows they would still be used, but likely it will not happen
in practice. What counts is that the build itself is running on which platform, not the target
platform.
Some generated files are written directly in an SConstruct or SCsub file, before the parallel build starts. They don't need to be written in a subprocess, apparently, so I left them as is.
|
|
|
|
Fix main scene file filter
|
|
Fix various missing arguments in bindings.
|
|
|
|
[Core] [Mono] Fix Color missing int export methods, added 64-bit
|
|
Removed incorrect Basis::set_scale().
|
|
This commit makes operator[] on Vector const and adds a write proxy to it. From
now on writes to Vectors need to happen through the .write proxy. So for
instance:
Vector<int> vec;
vec.push_back(10);
std::cout << vec[0] << std::endl;
vec.write[0] = 20;
Failing to use the .write proxy will cause a compilation error.
In addition COWable datatypes can now embed a CowData pointer to their data.
This means that String, CharString, and VMap no longer use or derive from
Vector.
_ALWAYS_INLINE_ and _FORCE_INLINE_ are now equivalent for debug and non-debug
builds. This is a lot faster for Vector in the editor and while running tests.
The reason why this difference used to exist is because force-inlined methods
used to give a bad debugging experience. After extensive testing with modern
compilers this is no longer the case.
|
|
These feature tags can be used to check whether the project was
started from an editor binary or from an export template binary.
|
|
|
|
|
|
|
|
Added a new MIDIDriver class
|
|
removed redundant strlen calculation from String::substr
|
|
Fix loading PO files with missing newline after last msgstr
|
|
|
|
Fixes #20375.
|
|
|
|
|
|
Mono: Add Dictionary and Array classes
|
|
Image trilinear scaling + Optimization
|
|
|
|
|
|
Soft body
|
|
|