Skip to content
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

New input types #3

Open
Geokureli opened this issue Nov 12, 2024 · 0 comments
Open

New input types #3

Geokureli opened this issue Nov 12, 2024 · 0 comments

Comments

@Geokureli
Copy link
Owner

Geokureli commented Nov 12, 2024

Various ideas for types of input types:

  • MouseScreenEdge(axis, distance:Float): x is 1.0 when the mouse is within distance pixels from the right edge, and -1.0 on the left side, similar y for top and bottom (1.0 for top). Often used in RTS games with large maps, i.e. Civ and Warcraft
  • CustomAnalog(x:()->Float, y:()->Float): Allows any custom analog input, useful for Flesh to Stone's on-screen mobile analog stick, or anything not covered by existing commands. Alternatively (or additionally), can be CustomAnalog(input:FlxActionInputAnalog), might not be possible to do with @:inputs tags
  • CustomDigital: Same as above but for digital, either CustomDigital(pressed:()->Bool) or CustomDigital(input:FlxActionInputDigital) or whatever
  • Input(input:IFlxInput): Allows attaching buttons, say if PAUSE uses a gamepad button on desktop but an on-screen button for mobile
  • add deadzone and axis to analog sticks
@Geokureli Geokureli changed the title New analog input types New input types Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant