Skip to content

Conversation

Geokureli
Copy link
Member

@Geokureli Geokureli commented Sep 19, 2025

Adds point.setXY(n) which is equivalent to set(n, n). also deprecates the single-arg use of point.set(n) where x is set to n and y is set to 0.

Eventually, in the next major version, set(x) will be deleted and in a later minor version it will be readded to behave like setXY which will then be deprecated

*
* @param n The X and Y coordinate of the point in space.
*/
public inline function setXY(n:Float):FlxBasePoint
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't function return FlxPoint instead of FlxBasePoint?

Copy link

@BernardoGP4504 BernardoGP4504 Sep 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't function return FlxPoint instead of FlxBasePoint?

Both are the same, FlxBasePoint is the underlying type of FlxPoint

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't function return FlxPoint instead of FlxBasePoint?

Both are the same, FlxBasePoint is the underlying type of FlxPoint

It still matters, this is a copy paste error, I think it's already fixed locally, but I'll check

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants