Input VS QField

Input is a commercial-grade library and is being used in Shovel Knight: Pocket Dungeon and Samurai Gunn 2 and many other titles. It has extensive documentation to help you get started. Inputs strips away the boring repetitive task of getting controls set up perfectly and accelerates the development of your game.

Do yourself a favour and check out / use Input by Juju Adams.

- Input: The game works seamlessly with controller or mouse and keyboard. I used JujuAdams' Input 5 to handle inputs from various controllers. Setting up key rebinding was easy and is good for accessibility. It's great for multiplayer and cross-platform, if I decide to do those later. I wish I had known about Input a long time ago.

Another one I love is Input (although it's a bit of overkill for most games): https://github.com/JujuAdams/input

If you haven’t seen it yet, I’d look into Input. It’s had an amazing amount of work put into it to make it as compatible as possible with input devices, has keybindings, etc. Definitely a timesaver when it comes to player input.

Turns out that this is a harder question to answer than you might expect. Input has a bunch of tools that you might find useful, but if you want the specific solution for keyboard constants that GM doesn't have natively then you'll find it here.

Consider checking out this comprehensive, easy to use and free input library: https://github.com/JujuAdams/Input

https://github.com/opengisch/QField lists windows, macos and linux too

and we love contributions :) https://github.com/opengisch/QField/blob/master/CONTRIBUTING.md

Someone knowledgeable with Android packaging and Qt is needed for F-droid, the renowned repository of free software apps for Android, to package QField, the official Android port of the renowned GIS software QGis.

The QField main GitHub repo