-
-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose Vector*
component-wise min/max
to scripting
#7439
Comments
Please explain why one would want to perform these operations, preferably with concrete examples. |
Here: #7333 (comment) Generally cases like tracking min/max grouped, can be used for audio with vectors, there are also some places in the code base that would benefit from the already existing functions, like It is also used in the engine in |
Just today i was trying to do this to get the maximum velocity vector along the axes. |
Describe the project you are working on
N/A
Describe the problem or limitation you are having in your project
Manually creating
min/max
vectors in GDScript is tedious and error prone, one use case is #7333 (comment)Describe the feature / enhancement and how it helps to overcome the problem or limitation
The built-in functions accomplish this task directly, and adds parity with other already exposed cases such as
floor
,clamp
,round
, etc.Having access to these would greatly reduce clutter, improve readability, and reduce errors
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
Expose the already existing component-wise
min/max
methods of these classesI already have a branch ready for this
If this enhancement will not be used often, can it be worked around with a few lines of script?
It can, but it is error prone
Is there a reason why this should be core and not an add-on in the asset library?
It relates to binds in core
The text was updated successfully, but these errors were encountered: