6 commits

Author	SHA1	Message	Date
VolTer	e26f0906f2	Implement snappedi, snappedf, and Vector[2/3/4]i.snapped	2022-11-19 06:18:55 +01:00
Rémi Verschelde	d9a3888cea	Merge pull request #66133 from aaronfranke/set-all ... Delete `set_all`, `set_axis`, and `get_axis` methods from Vector2/3/3i/4/4i	2022-10-03 09:23:46 +02:00
Aaron Franke	50fb0220ca	Define AXIS_COUNT in all vector types	2022-09-19 17:50:35 -05:00
Aaron Franke	fd8bd27657	Remove set_axis and get_axis methods from Vector2/2i/3/3i/4/4i	2022-09-19 15:08:50 -05:00
Aaron Franke	058ac331b0	Minor fixes to Vector4	2022-09-04 20:38:44 -05:00
reduz	455c06ecd4	Implement Vector4, Vector4i, Projection ... Implement built-in classes Vector4, Vector4i and Projection. * Two versions of Vector4 (float and integer). * A Projection class, which is a 4x4 matrix specialized in projection types. These types have been requested for a long time, but given they were very corner case they were not added before. Because in Godot 4, reimplementing parts of the rendering engine is now possible, access to these types (heavily used by the rendering code) becomes a necessity. **Q**: Why Projection and not Matrix4? **A**: Godot does not use Matrix2, Matrix3, Matrix4x3, etc. naming convention because, within the engine, these types always have a *purpose*. As such, Godot names them: Transform2D, Transform3D or Basis. In this case, this 4x4 matrix is _always_ used as a _Projection_, hence the naming.	2022-07-23 14:00:01 +02:00