HaxeFlixel / HaxeFlixel/flixel
Suggestion for default pixelPerfectRender and pixelPerfectPosition
Nobody has claimed this yet.
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
There needs to be a way of setting the default of pixelPerfectPosition. After some thought, and some issues with the way defaults can be set for pixelPerfectPosition, I do not think the existing way for pixelPerfectPosition is sufficient.
Recently (since the last release, I think) it was made possible to set pixelPerfectRender per camera. This somewhat provides a way of having a "default" value, but it is far from perfect. For example, if you have many cameras, you have to set it on all camera. Furthermore, there is some undefined and complicated behavior for combinations of trues/falses/nulls between the cameras and sprites.
I'm wondering if it might be better to be able to change the default values for pixelPerfectRender and pixelPerfectPosition in the project xml? This would still make it possible to set the values depending on platform, but in a more convenient way.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the project XML configuration handling and the code that resolves pixelPerfectRender and pixelPerfectPosition across cameras and sprites. Review how true, false, and null are currently combined; done means a documented project-level default works consistently while preserving per-camera and per-sprite behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100