-
Notifications
You must be signed in to change notification settings - Fork 454
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
Add FlxPointer as a base class for FlxTouch and FlxMouse, closes #1088 #1099
Conversation
I don't like the name of this class, having numbers in class names is just weird. Couldn't we name it |
FlxPointer works for me. |
@@ -44,6 +44,7 @@ class FlxTypedGroup<T:FlxBasic> extends FlxBasic | |||
@:allow(flixel.FlxObject) | |||
@:allow(flixel.tile.FlxTilemap) | |||
@:allow(flixel.system.FlxQuadTree) | |||
@:allow(flixel.input.FlxPointer) | |||
private static inline function resolveGroup(ObjectOrGroup:FlxBasic):FlxTypedGroup<FlxBasic> |
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.
Can we move these private static functions to the bottom of the class? I always prefer to list public fields / methods before privates.
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 thought we agreed on putting static fields to the top?
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 don't think private fields should go above public fields, static or not.
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.
Imo, order should be:
public static
public
private static
private
Add FlxPointer as a base class for FlxTouch and FlxMouse, closes #1088
No description provided.