TASEmulators / TASEmulators/BizHawk

Judging Feature Proposal/Request: Show/Hide used/unused columns in TAStudio

Open
#4,548 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Request: Feature/Enhancement Tool: TAStudio
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

When it comes to judging various systems, showing all the possible input columns in TAStudio can make following an author's inputs difficult, as it is often not feasible to fit all the possible input columns on-screen at any given moment. This can sometimes make folowing what an author did more tedious as it requires one of the following approaches:

  1. Pausing the playback for every vertical screen of frames and then laterally scrolling through all input possibilities to see where the actual used inputs are
  2. Grouping input columns into used/unused and keeping all the used input columns together within TAStudio in an attempt to fit them all on the screen at once. While this can be done by manually turning off any unused column from the "Columns" menu, this still requires manually observing the entirety of the run simply while watching for where inputs are/aren't in the run in order to know if a column is even used in the first place.

We currently have a 'show keys' option in the "Columns" menu of TAStudio that toggles all the keys as shown/hidden, but it does not distinguish if a particular input column is used within the run.

Would it be possible to get an option under "Columns" to either of the following?
  • show only used input columns
  • hide unused input columns

I realize this may require some significant colding to allow BizHawk/TAStudio to programmatically parse a .bk2 fully to know which input columns are used, but I figured I'd ask anyway.

Moved from https://github.com/TASVideos/tasvideos/issues/2232.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in TAStudio's Columns menu and trace the existing “show keys” option to understand how columns are shown or hidden. Determine how a .bk2 run can identify input columns used anywhere in the run; done means an option can show only used columns or hide unused ones while preserving current column controls.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.