Controles táctiles

From DDraceNetwork
Revision as of 03:22, 26 December 2024 by NoKetchup (talk | contribs) (Created page with "El elemento raíz en el archivo JSON debe ser un objeto. El atributo <code>"touch-buttons"</code> del objeto raíz especifica un arreglo de objetos de botones táctiles. Cada objeto de botón táctil tiene las siguientes propiedades ajustables:")
Other languages:

Los controles táctiles fueron agregados al cliente DDNet en la versión 18.8, para la cual también se publicó la primera versión más reciente para Android. La versión de DDNet anterior para Android es la 9.3.1, para la cual existe un tutorial separado. Ahora solamente se considerarán los controles táctiles desde la versión 18.8 en adelante.

La interfaz de usuario se puede usar con los controles táctiles de las siguientes maneras:

  • Toca donde sea para mover el cursor y hacer la acción de clic izquierdo.
  • Toca y mantén por al menos 0,5 segundos en la misma posición para hacer la acción de clic derecho.
  • Usa dos dedos para para desplazarte hacia arriba y abajo en listas desplazables como el navegador de servidores y en la consola.
  • En Android: Usa el botón (virtual) Volver como tecla Escape para cerrar menús y demás.

Los controles táctiles pueden ser activados o desactivados con la variable de configuración cl_touch_controls, la cual por defecto es 1 en dispositivos Android y 0 en otras plataformas. Los controles táctiles deberían tambien funcionar en otras plataformas que permitan dispositivos táctiles, pero esta guía justamente fue probada en Android.

Los controles táctiles consisten en varios botones en pantalla, los cuales son mostrados dependiendo del contexto en el que se usen. Por ejemplo: los botones para el movimiento son solamente mostrados cuando se está dentro del juego.

Configuración predeterminada de los botones táctiles

Captura de pantalla de los controles táctiles predeterminados dentro del juego.

Los botones para moverse a la derecha, izquierda y saltar están ordenados en forma de ⊥, similar a WASD.

Para las acciones de disparar y usar el gancho existen dos modos:

  1. Entrada táctil directa: el ratón se mueve exactamente en donde el jugador toca la pantalla.
  2. Joystick virtual: un botón es usado para emular un joystick, en el cual el movimiento del ratón es relativo al centro de la pantalla.

En cualquiera de los modos, se utiliza un botón para alternar entre las acciones activas (disparar y enganchar). Mientras se mantiene presionado el joystick virtual, este botón ejecuta directamente la otra acción en lugar de cambiarla.

El modo de entrada táctil directa puede ajustarse por separado para jugar y observar, evitando así entradas táctiles accidentales al usar un joystick.

Al observar, se utiliza la entrada táctil directa para desplazarse por el mapa directamente, como en un visor de imágenes o mapas. También se pueden usar los joysticks virtuales para desplazarse por el mapa mientras observas.

Dos botones separados son mostrados para cambiar al arma siguiente o anterior.

Captura de pantalla de los controles táctiles predeterminados en el juego, con todos los botones visibles.

Se utiliza un botón de menú tipo hamburguesa ☰ para alternar la visibilidad de botones de menor uso. Esto incluye botones para mostrar la tabla de puntuación, el selector de emoticonos, el menú de espectador, abrir el chat general y el de equipo, votar sí/no y hacer zoom. Mantener presionado el botón tipo hamburguesa abrirá el menú del juego.

Cuando se contecta el dummy, se muestra un botón para cambiar entre dummys.

El selector de emoticonos y el menú de espectador se activan con sus respectivos botones y pueden ser desactivados al tocar fuera de ellos o usando el boton de volver. Actualmente, alternarlos mientras se mantiene presionado el botón táctil en el juego no es factible y resulta poco práctico, al menos en el caso del menú de espectadores.

Formato de configuración de botones táctiles

La disposición predeterminada de los botones descrita anteriormente se carga desde el archivo touch_controls.json en el directorio data, el cual no debe ser modificado. Esta disposición puede ser sobrescrita creando un archivo touch_controls.json en el directorio de configuración.

La configuración de los botones táctiles es un archivo de texto en formato JSON. Se recomienda aprender primero los conceptos básicos del formato JSON para comprender la siguiente guía. La configuración debe ser un archivo JSON válido. Existen guías y herramientas de validación para el formato JSON disponibles en internet. La estructura del archivo JSON se describe a continuación.

El elemento raíz en el archivo JSON debe ser un objeto. El atributo "touch-buttons" del objeto raíz especifica un arreglo de objetos de botones táctiles. Cada objeto de botón táctil tiene las siguientes propiedades ajustables:

  • Position and size (attributes "x", "y", "w", "h"): the X/Y position and width/height are integers on a 1,000,000² grid. These unit grid values are converted to screen grid values at runtime in relation to the size and aspect ratio of the screen. This means buttons may appear stretched if the resolution is changed, but it allows us to provide a reasonable default for slightly different aspect ratios.
  • Shape (attribute "shape"): determines the shape of the button being rendered.
    • "rect": rectangle shape.
    • "circle": circle shape. The button size will automatically be adjusted so that width and height are identical.
  • Visibility (attribute "visibilities"): an array of predefined visibility classes can be selected and the button is only shown if all conditions are satisfied. An empty array means that the button is always shown. The following visibility classes are defined:
    • "ingame": player is ingame, i.e. not spectating.
    • "extra-menu", "extra-menu-2", "extra-menu-3", "extra-menu-4", "extra-menu-5": the extra menu with the given number is activated.
    • "zoom-allowed": zoom is allowed on this server.
    • "vote-active": a vote is currently active.
    • "dummy-allowed": dummy is allowed on this server.
    • "dummy-connected": dummy is currently connected.
    • "rcon-authed": player is currently authed in rcon.
    • "demo-player": demo player is currently active.
    • All visibility classes can be inverted by prefixing them with -, e.g. "-ingame" is satisfied when the player is not ingame, i.e. spectating.
  • Behavior (attribute "behavior"): an object which describes the behavior of this touch button when it is activated/deactivated as well as its label. The attribute "type" is used to differentiate which type of behavior is used. The behavior is either predefined (hard-coded) or based on generic console commands (like binds). Predefined behavior is only used where necessary, all other buttons are represented as generic binds.
    • Predefined behavior (attribute "type" set to "predefined"): The attribute "id" is set to a fixed string value which determines the specific predefined behavior. The following predefined behaviors can be used:
      • "ingame-menu": Opens the ingame menu immediately when released.
      • "extra-menu": The extra menu button which toggles visibility of buttons with "extra-menu", "extra-menu-2", "extra-menu-3", "extra-menu-4" and "extra-menu-5" visibilities. Also opens the ingame menu on long press.
        • The attribute "number" specifies an integer between 1 and 5 to associate this button with the respective visibilities "extra-menu", "extra-menu-2", "extra-menu-3", "extra-menu-4", "extra-menu-5".
      • "emoticon": Opens the emoticon selector (this does not work with binds).
      • "spectate": Opens the spectator menu (this does not work with binds).
      • "swap-action": Swaps the active action (fire and hook) for direct touch input and virtual joysticks.
      • "use-action": Uses the active action with the current aiming position.
      • "joystick-action": Virtual joystick which uses the active action.
      • "joystick-aim": Virtual joystick which only aims without using an action.
      • "joystick-fire": Virtual joystick which always uses fire.
      • "joystick-hook": Virtual joystick which always uses hook.
    • Bind behavior (attribute "type" set to "bind"). Buttons with this behavior execute console commands like regular key binds.
      • The attribute "label" specifies as a string the label of the button.
      • The attribute "label-type" specifies as a string the type of the label of the button, i.e. how the attribute "label" is interpreted:
        • "plain": Label is used as is.
        • "localized": Label is localized. Only usable for the default buttons for which there are translations available.
        • "icon": Icon font is used for the label. Icons must be encoded in UTF-16 using \uXXXX, e.g. \uf3ce for the mobile phone icon which has unicode f3ce. Note that the icon must be available in the icon font that comes with DDNet, Font Awesome Free.
      • The attribute "command" specifies as a string the command to execute in the console like a bind when this button is used, e.g. "+fire" for a button that uses the fire action.
    • Bind toggle behavior (attribute type set to "bind-toggle"). Buttons with this behavior cycle between executing one of two or more specified commands.
      • The attribute "commands" specifies an array of two or more commands in the order in which they are shown and executed. Each command is an object with the attributes "label", "label-type" and "command" which are defined the same as for the bind behavior described above. At least two command objects must be specified in the array.

The root object additionally has the following attributes:

  • "direct-touch-ingame": specifies the mode of direct touch input while ingame. Possible values:
    • "disabled": Direct touch input is not used while ingame. This means a virtual joystick is necessary.
    • "action": Direct touch input uses the active action (see above).
    • "aim": Direct touch input only changes the aiming position without using an action. This means separate buttons for using the actions are necessary.
    • "fire": Direct touch input always uses fire.
    • "hook": Direct touch input always uses hook.
  • "direct-touch-spectate": specifies the mode of direct touch input while spectating. Possible values:
    • "disabled": Direct touch input is not used while spectating. This means a virtual joystick is necessary.
    • "aim": Direct touch input is used for spectating.

Ingame menu buttons

Screenshot of the additional buttons in the ingame menu when touch controls are enabled.

In addition to the separate on-screen touch controls, a second row is added to the main page of the ingame menu when cl_touch_controls is enabled for less frequently used functions which are otherwise not usable without a keyboard:

  • Buttons to open the local and remote consoles. Opening the local console without the touch controls is useful because error messages would be shown there if the touch controls configuration could not be loaded.
  • Button to close the menu, which is more convenient than using the virtual back button if it's not always shown.
  • Checkbox for toggling the touch controls editor UI (see below).

Ingame touch controls editor

Screenshot of the ingame touch controls editor user interface.

The user interface to adjust the touch controls is rendered over the main screen of the ingame menu when enabled. For now, the touch controls editor is limited to basic configuration management functions.

  • Saving the configuration to the touch_controls.json file in the config directory.
  • Discarding the current changes by reloading the touch_controls.json file from the config directory.
  • Restoring the default configuration by reloading the touch_controls.json file from the data directory.
  • Displaying whether there are unsaved changes.
  • Importing and exporting the configuration from and to the clipboard. This is the only way to edit the configuration on newer Android versions, as editing files within apps' storage is not possible anymore.

Furthermore, the global touch controls settings can be adjusted in this UI:

  • The direct touch input modes while ingame and spectating (see Touch button configuration format) can be adjusted using dropdown menus.

While the touch controls editor is active, all touch buttons are shown regardless of their visibilities, to better support arranging the buttons.

Adjusting the controls

  1. Export the touch configuration to the clipboard.
  2. Save the clipboard to a file so you can more easily edit it. You should also do this to have a backup of your configuration!
  3. Edit the configuration (see above for details about the format).
  4. Copy the edited configuration to the clipboard and import it in the client again. If the configuration could not be loaded successfully, check the local console for error messages containing touch_controls and fix the configuration accordingly. Use online tools for JSON validation and formatting.
  5. Save the changes in the client when you are done. You can also discard your changes or revert to the default if you messed up.

A more convenient user interface to edit the touch controls directly in the client is planned.

Note: You can also edit the file touch_controls.json in the config directory directly instead of exporting/importing to/from the clipboard, but this is not supported on Android.

Examples

Example for the overall structure of the touch configuration: 

{
    "direct-touch-ingame": "action",
    "direct-touch-spectate": "aim",
    "touch-buttons": [
        ...
    ]
}

Example button with "bind" behavior that echos a message in chat: 

{
    "x": 500000,
    "y": 500000,
    "w": 100000,
    "h": 100000,
    "shape": "rect",
    "visibilities": [
    ],
    "behavior": {
        "type": "bind",
        "label": "Example",
        "label-type": "plain",
        "command": "echo Hello world!"
    }
}

Example button with "predefined" behavior for a virtual joystick that uses the active action: 

{
    "x": 755000,
    "y": 580000,
    "w": 225000,
    "h": 400000,
    "shape": "circle",
    "visibilities": [
        "ingame"
    ],
    "behavior": {
        "type": "predefined",
        "id": "joystick-action"
    }
}

Example button with "bind-toggle" behavior that switches between echoing three different messages in chat: 

{
    "x": 600000,
    "y": 200000,
    "w": 100000,
    "h": 100000,
    "shape": "rect",
    "visibilities": [
    ],
    "behavior": {
        "type": "bind-toggle",
        "commands": [
            {
                "label": "Echo 1",
                "label-type": "plain",
                "command": "echo 1"
            },
            {
                "label": "Echo 2",
                "label-type": "plain",
                "command": "echo 2"
            },
            {
                "label": "Echo 3",
                "label-type": "plain",
                "command": "echo 3"
            }
        ]
    }
}

Known issues

  • Problem on Android: Pressing down 3 or more fingers at the same times causes all fingers to be released immediately.
    • Solution: This is caused by features of your phone that handle global gestures with multiple fingers. Open the Settings app and disable gesture features that involve 3 or more fingers (search for "3 fingers"). In particular, disable the "Swipe down with 3 fingers to take screenshot", "Touch and hold with 3 fingers to take screenshot" and "Swipe up with 3 fingers to enter Split View" features.
  • Problem on Android: Rarely, touching in the top around 15% of the screen does not work at all or very inconsistently.
    • Solution: It is unclear what causes this. It should be fixed by restarting the app. Going back to the home screen may also fix it.

Implementation details

These are details about the implementation of the touch controls intended for developers.

The ingame touch controls are implemented in a separate client component CTouchControls in the files src/game/client/components/touch_controls.cpp and src/game/client/components/touch_controls.h. Whenever possible, binds are used directly as button behavior instead of using predefined behavior to reduce complexity.

When adding your own button behavior in a forked client it is recommended to prefix names of new shape, visibility, behavior etc. with the name of your fork, e.g. myfork.octagon if you add a new shape for octogonal buttons, to prevent conflicts in future versions.

To add touch support for other ingame client components like the emoticon wheel and spectator menu, use the CUi::UpdateTouchState function like for the emoticon wheel and spectator menu. Ensure that your component handles KEY_ESCAPE to close itself, which also corresponds to the Back-button on Android. Note that only one component may use the touch state in each frame, so it is not possible to hold an ingame touch button and use another component like the emoticon wheel at the same time with other fingers. Instead, the respective predefined touch button behavior (e.g. CSpectateTouchButtonBehavior) only activates the ingame component (e.g. the spectator menu) in its OnDeactivate function but does not deactivate it again. Activating the component in the OnActivate function already would cause the finger that activated the button to also affect the activated component.

References

Retrieved from "https://wiki.ddnet.org/index.php?title=Touch_controls/es&oldid=38070"