HaxeFlixel / HaxeFlixel/flixel
Improve FlxSwipe
Nobody has claimed this yet.
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
Right now, FlxSwipes are only created after mouse or touch is released, which is not how I expected them to work. So I decided to improve it a little: a FlxSwipe will be created as soon as a mouse button or touch is down and kept in FlxG.swipes until mouse/touch is released and its endPosition is updated every frame.
And I'm feeling like this is not enough. I think FlxSwipe also needs a threshold since a click or a tap is also counted as a swipe. What about a swipe going in different directions (like circling, ping pong)? Should we add FlxPoints between start and end position like a path?
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 FlxSwipe and FlxG.swipes, then trace how mouse and touch input currently creates and updates swipes. The issue proposes several unresolved behaviors—creation on press, per-frame endPosition updates, thresholds, direction changes, and path points—so completion requires deciding which scope and behavior to implement. No tests or specific files are named.
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
- Needs clarification
- Newbie friendliness
- 20/100