-
Notifications
You must be signed in to change notification settings - Fork 435
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
Remove unused stuffs #3228
Remove unused stuffs #3228
Conversation
flixel/FlxCamera.hx
Outdated
static var renderPoint:FlxPoint = FlxPoint.get(); | ||
static var renderPoint:FlxPoint = new FlxPoint(); | ||
|
||
static var renderRect:FlxRect = FlxRect.get(); | ||
static var renderRect:FlxRect = new FlxRect(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why change this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its incorrect usage, since its a static it is only ever gotten once. And never .put(). And if someone were to use .put on it it would break
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree that it's "incorrect", it makes absolutely no difference
flixel/flixel/math/FlxPoint.hx
Lines 300 to 303 in 94dbde5
public inline function new(x:Float = 0, y:Float = 0) | |
{ | |
this = FlxPoint.get(x, y); | |
} |
plus, using get
isn't an indication that it's okay to call put
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh i didnt know it was changed. It used to make a difference before the reworked in commit e721fca. Should i revert the commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What difference did it make? I don't understand what you're referring to, or why we would revert anything
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eh just forget it. Do i need to do anything?
e7d9c00
to
959267b
Compare
I'm not interested in these changes at the moment, at some point I'd like to assess whether we can add blendmode support back in, until then I'd leave it as is |
This was used when FLX_DRAW_TILES still existed. And quads still uses blend modes with overrideBlendMode() in flxdrawquaditem |
I'm aware, as I said, I think before we gut it we should see if it can be reimplemented |
This removes some old stuff which was no longer used.