You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The transform.position vector x and y values for Node2D and Node3D have a fixed 3 decimal point precision, rather than following the interface/inspector/default_float_step value as they should. This is very limiting, and doesn't match the behavior of the scale value. Though this is related to #18251, it's not the same, as most of the problems described in that issue were resolved by adding interface/inspector/default_float_step, which the transform.position originally followed.
Upon initial investigation, it seems to have been caused by PR #57144, which was to fix a different issue where one was unable to click and drag to change the position values. It seems that the best solution would be to modify the ADD_PROPERTY lines for position to simply omit the step value, which will indicate that it should use the interface/inspector/default_float_step value rather than the current hardcoded 0.001 value.
Steps to reproduce
In the editor settings set the interface/inspector/default_float_step value to something more precise than 3 decimal points, for example 0.0000001
Add or edit a Node2D (or any subclass)
Attempt to set a Position with more than 3 decimal places (for example 0.111111), then hit enter
Result: the value gets rounded to 3 decimal places (for example 0.111)
Note that the scale value works properly in 4.3 (though it didn't work properly in 4.0)
Minimal reproduction project (MRP)
N/A
The text was updated successfully, but these errors were encountered:
Tested versions
System information
Windows 10 - Godot v4.3.stable.official [77dcf97]
Issue description
The
transform.position
vector x and y values for Node2D and Node3D have a fixed 3 decimal point precision, rather than following theinterface/inspector/default_float_step
value as they should. This is very limiting, and doesn't match the behavior of the scale value. Though this is related to #18251, it's not the same, as most of the problems described in that issue were resolved by addinginterface/inspector/default_float_step
, which thetransform.position
originally followed.Upon initial investigation, it seems to have been caused by PR #57144, which was to fix a different issue where one was unable to click and drag to change the position values. It seems that the best solution would be to modify the
ADD_PROPERTY
lines forposition
to simply omit the step value, which will indicate that it should use theinterface/inspector/default_float_step
value rather than the current hardcoded0.001
value.Steps to reproduce
interface/inspector/default_float_step
value to something more precise than 3 decimal points, for example 0.0000001Note that the scale value works properly in 4.3 (though it didn't work properly in 4.0)
Minimal reproduction project (MRP)
N/A
The text was updated successfully, but these errors were encountered: