Skip to content

Releases

recomp-common 0.5.0

Choose a tag to compare

@tmcleroy tmcleroy released this 15 Oct 18:19
  • In-game menu: a description longer than three lines no longer runs over the hint at the panel's
    foot. The panel leaves room for the longest description on the page (three lines at least), and
    the rows close up when the picture is short.
  • In-game menu: a value too long for the room beside its title (a long choice's name) is drawn in
    the small letters, and cut short with ".." if even those do not fit, instead of over the title.
  • In-game menu: the panel is opaque; the game's own text no longer shows faintly through it.
  • In-game menu: Right on a page's row goes into that page, as Confirm does (Left still comes back).
  • The launcher's Features page has a search box. Only the features with every word typed in
    their name, description, category or choices are shown, with how many of them match. Ctrl+F (or
    Cmd+F) goes into it; Esc empties it, a second Esc leaves it; with a gamepad, A goes into it and B
    leaves it with what was typed kept. The other pages' pictures are the same bytes as before.
  • Launcher tests: --press takes f for Ctrl+F and types what is between double quotes.

recomp-common 0.4.0

Choose a tag to compare

@tmcleroy tmcleroy released this 13 Oct 17:30
b35e4f3
  • The launcher works with a gamepad, and with the arrow keys, alone. The d-pad, the left stick
    or the arrow keys move a ring from one button, switch, list or sidebar row to the next; A, Space
    or Enter presses what the ring is on; B or Esc closes a list, or goes from a page to the sidebar;
    the shoulder buttons go to the page before and after; the right stick scrolls a page. In the
    sidebar, up and down change the page and right goes into it (at its first control); the ring
    never jumps from a sidebar row to whatever in the page happens to be nearest. With a gamepad connected the ring
    is shown from the start; using the mouse hides it. A launcher nobody presses a key in looks as it
    did: its pages' pictures are the same bytes.
  • A game file can be chosen with a gamepad: Choose, pressed with one, opens a list of folders and
    files in the launcher's own window (the system's file dialog wants a mouse or a keyboard).
  • Choosing a button on the Controllers page with a gamepad: the button pressed is the button
    chosen and nothing more; while a key is waited for, any gamepad button leaves things as they were.
  • Muted: the Game page has a Sound card with one switch, off unless the player switches it on.
    When it is on the game is started with --mute after the port's own arguments
    (Description::mute_argument; nullptr for no card). A game should take that argument and have
    a row in its menu that switches the sound off and on.
  • Menu: a MenuRow::Mute row ("Sound": On / Muted) through MenuConfig::muted and setMuted
    (RMENU_ROW_MUTE for C). kMenuBack now leaves a page for the one it was reached from and closes
    the menu only on the first page (it closed the menu from anywhere). A host should give Space,
    Enter and a gamepad's A to Confirm, and Backspace and B to Back.
  • ui.h: focus_item, focus_next_item, show_focus, focus_shown, gamepad_in_use, and
    nav_item takes reachable. A port's own pages get the ring from the widgets they already use.
  • --screenshot PREFIX --press KEYS presses keys, and the buttons of a gamepad made for the test,
    then takes one picture: the launcher's navigation can be checked with no window and no gamepad.