TASEmulators / TASEmulators/BizHawk

TAStudio autosave's default is to overwrite movies without asking

Open
#4,063 14 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

This probably isn't a new issue. Autosave is on by default and it will overwrite your tasproj without asking.

To me, it's clearly wrong to overwrite the current tasproj by default. All other applications that I'm aware of save to a secondary file that can be used as the restore point if you forget to save. It barely has to change the workflow. If the user manually saves, the secondary file can be deleted. If there's a secondary file upon load the program can prompt something like "An autosaved backup file for the current project was found. Would you like to restore it?"

Current behavior will mercilessly overwrite if you made changes you don't want to keep, accomplishing the opposite of the intended purpose.

(Personally, I have grown accustomed to just disabling Autosave upon first launch because autosave used to be a major interruption. It still can interrupt flow, and I prefer to choose when I have it saved.)

Host Env.

I had this occur just now in ed676cda391d25bdb1728ada13b7df21c0a974df

Also confirmed this behavior in 2.9.1

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 by tracing TAStudio's Autosave behavior and the tasproj load/save flow. Check how autosave currently selects its output and how loading handles an existing project, then compare the result with the requested secondary backup and restore prompt behavior. Done means autosave no longer overwrites the current tasproj by default and the proposed restore flow is handled safely.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.