Move some statics to `FlxG` (?)

Open
#2,951 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Domain
game-dev

Research direction

Start by comparing the existing statics in FlxSprite, including defaultAntialiasing, with the FlxG singleton. Determine which statics are being considered and whether moving them is intended; the issue is complete only when that scope and the migration approach are agreed.

Written by the indexing model from the issue text.

Description

I've seen @Geokureli talk a lot about how he regrets about adding some statics in different classes, such as FlxSprite.defaultAntialiasing. They are actually useful in many cases, but wouldn't moving those variables into the FlxG singletone makes more sense?

Dominant language
Haxe
Stars
2.2k
Forks
522
Avg merge
34m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HaxeFlixel/flixel

All issues in HaxeFlixel/flixel

Similar issues

More Game Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.