Avoid manually inserting input binding

LeeTeng2001 · September 6, 2021, 8:04am

Hi guys, is there a way to quickly input input bindings without having to scroll through the list, find them and add them one by one? (like searching through the list or auto detect input), it’s killing me

britzl · September 6, 2021, 8:26am

@LeeTeng2001 unfortunately not at the moment

LeeTeng2001 · September 6, 2021, 8:47am

thanks for the quick reply, I really like how clean defold looks and use but tilemap and input is killing my workflow , thank you tho !!

britzl · September 6, 2021, 9:44am

I understand, but fortunately the input is something you usually set up once per project, and not every day. There is also an input binding file in builtins with all keys already bound to an action. The actions are a bit generic, like key_a, key_space etc, but it could work as a nice shortcut for you.

Also, note that you can edit all files as normal text files if that would help speed up your workflow.

There’s definitely room for improvement with tilemap editng. You can use an external tool such as Tiled since it has direct export to the Defold format.

LeeTeng2001 · September 6, 2021, 9:31am

WOW! I didn’t know that, I just checked the input file and indeed it’s human readable so it’s possible to write external script to automate the task, can I ask is the input name defined in this github file?

github.com

defold/defold/blob/1ae302ec33d4514408c04ad3ae5d3c1efe2057bd/engine/hid/src/glfw/hid_native.cpp

// Copyright 2020 The Defold Foundation
// Licensed under the Defold License version 1.0 (the "License"); you may not use
// this file except in compliance with the License.
//
// You may obtain a copy of the License, together with FAQs at
// https://www.defold.com/license
//
// Unless required by applicable law or agreed to in writing, software distributed
// under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
// CONDITIONS OF ANY KIND, either express or implied. See the License for the
// specific language governing permissions and limitations under the License.

#include "hid.h"

#include <assert.h>
#include <string.h>

#include <dlib/log.h>
#include <dlib/utf8.h>
#include <dlib/dstrings.h>

This file has been truncated. show original

I will take a look at Tiled, thanks again! I hope you have a great day sir

Mathias_Westerdahl · September 6, 2021, 9:47am

This is true for most of our formats. Scriptability being one of the reasons.

can I ask is the input name defined in this github file?

Not sure what you mean?
If you’re looking for the data format, it’s specified in the .proto file here:

github.com

defold/defold/blob/1ae302ec33d4514408c04ad3ae5d3c1efe2057bd/engine/input/proto/input_ddf.proto

package dmInputDDF;

import "ddf/ddf_extensions.proto";
import "ddf/ddf_math.proto";

option java_package = "com.dynamo.input.proto";
option java_outer_classname = "Input";

enum Key
{
    KEY_SPACE = 0;
    KEY_EXCLAIM = 1;
    KEY_QUOTEDBL = 2;
    KEY_HASH = 3;
    KEY_DOLLAR = 4;
    KEY_AMPERSAND = 5;
    KEY_QUOTE = 6;
    KEY_LPAREN = 7;
    KEY_RPAREN = 8;
    KEY_ASTERISK = 9;

This file has been truncated. show original

britzl · September 6, 2021, 10:28am

Yes, this is important as it is easier to deal with merge conflicts if all files are text based.

We use Google protobuf as the data format. At runtime we use binary format, but while editing we use the text format.