Skip to content

Firmware UX improvements, mainly re: status #3974

@YoshiRulz

Description

@YoshiRulz
  • The invariant of "exactly 1 Ideal option per record" is currently broken, both by records with multiple Ideal options, and I think by a couple records with none. This restriction on humans has been lifted and the documentation changed to match the existing behaviour.
  • The autodetect code (in FirmwareManager IIRC) chooses the first record which can be resolved to a file. But that means, if you had both an Ideal and an Acceptable firmware in your firmware dir, it might use the Acceptable one. This could be fixed by ensuring the options list is sorted by status.
  • A review of which firmwares work and which don't might be warranted, but once you start testing games, there's no obvious cut-off point. The requirements could grow indefinitely. So maybe just... have TASVideos judges read them over? judges apparently not interested, moved to https://gitlab.com/YoshiRulz/yoshis-hawk-thoughts/-/issues/219

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    App: EmuHawkRelating to EmuHawk frontendMetaRelating to code organisation or to things that aren't codeNeeds domain knowledge for triagehelp wantedWe'd love to have this feature, but no dev is working on it. Discussion and PRs are welcome.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions