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

Input Map should not have forced defaults, but optional default sets. #428

Closed
AlexZan opened this issue Feb 1, 2020 · 1 comment
Closed
Labels

Comments

@AlexZan
Copy link

AlexZan commented Feb 1, 2020

I have seen similar requests, and the similar arguments made against them:

godotengine/godot#17210
#303

The main argument against this type of request is that these default input mappings are required for the ui. My argument against that is as follows:

Input Map, or anything for that matter should be opinionated, by default. Behaviour/Opinion should be contextual. For example, If I am making a simple 3d prototype, that has no interest in ui, and does not want the clutter of current default settings, it should not be forced.

If a developer is working on a project that requires the type of UI that the current default input map is made for, they can load it in from a list of default presets, or download/add it. There could eventually be several for different common game types.

Starting with a blank state will allow developers to have better focus and more organic growth to their project.

I am prototyping about 20 different projects, many of them have conflicts with the default input map. It should not be forced, but optional.

@Calinou
Copy link
Member

Calinou commented Feb 1, 2020

Duplicate of #303. Please write a comment in that proposal instead of opening a new proposal 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants