Skip to content

Input handling should stop on command #55

@skinnyjames

Description

@skinnyjames

Noticing when using nk_edit_string that text handling can be a bit erratic.

An example is triggering Select All which is Ctrl + A.
raylib-nuklear correctly processes this input, but also keeps going through the rest of the keys, so what ends up happening for me is

  1. Enter text
  2. Press Ctrl + a
  3. The text is selected, and a is immediately inserted over the selection.

Expected behavior

nk_raylib_input_keyboard returns after an atomic command is captured.

Actual behavior

Commands run in succession unintentionally.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions