Make navmesh rasterization on the navigation regions and map more lenient by starting out with a lower internal cell scale by default and changing the merge error to just warning that can be toggled.
(cherry picked from commit 19df15f1dc)
xml codeblock indentation was changed from spaces to tabs but the tabs
were being replaced with empty strings when exported with
--dump-extension-api-with-docs, this is small change so that tab
characters are no longer replaced.
(cherry picked from commit e9131550b1)
Updated Array::resize() to call ptrw() once before looping to initialize typed array elements, instead of accessing each through .write[].
(cherry picked from commit 4c3f2be16d)
SDL input driver did not have the "xinput_index", "raw_name", "vendor_id" and "product_id" fields for this method and exposed an additional, essentially useless for the users "mapping_handled" field. This commit fixes these issues.
Adds a note in the docs that a thread count of 0 has the same effect as a thread count of -1.
Change language of WorkerThreadPool in ProjectSettings
Co-Authored-By: Tomasz Chabora <kobewi4e@gmail.com>
----
Extension EditorPlugins added during Hot Reload on Initialization level
Editor were being attached to the scene tree before all the GDExtension
Classes (such as already loaded resources) are re-initialized.
This fixes a recent regression. In theory, low priority tasks should always go to the queue and never be executed on the calling thread. However, when using NO_THREADS build, all tasks need to execute on the calling thread.
This is necessary because we will always deadlock if a thread takes on multiple pump tasks since pump tasks never return.
This means when using separate threads for certain systems (like physics or rendering), we need to be sure that there are enough threads to have at least one per system (to ensure forward progress).
configured `InputEvent` in the plugin
This allows undo and redo, and can mark in time whether the handled
`InputEvent` resource is edited.
`command_or_control_autoremap` needs to be handled separately, as
its value will change the usage of other properties.
- Now you can get the ContainerTypeValidate from a Dictionary (both for
keys and for values).
- ContainerTypeValidate exposes a validator function that does not show
any error in case of failure. This allows testing values before trying
to use them in Dictionary.