feat(saves): Open saves folder and Open builds folder buttons #185
No reviewers
Labels
No labels
area/build
area/install
area/saves
area/tooling
area/ui
area/updates
ci: approved
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher!185
Loadingā¦
Reference in a new issue
No description provided.
Delete branch "dyst/LongshotLauncher:feat/open-folders"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Players who want to look at their saves or builds, or copy them by hand, had to know where the launcher keeps them. Now one click opens each folder in the file manager.
Stacked on #184: merge order #182, #184, then this (#180 and #181 are merged).
What changed
savefolder, the one every build shares (%APPDATA%\Longshot\save\on Windows,~/.local/share/longshot/save/on Linux, a portable launcher'sLongshotLauncher-data\user\save\). Its tooltip shows the path.Host.Open, the same as a build row's Open folder: Explorer on Windows,xdg-openon Linux and the Steam Deck.SaveEnvironment.SaveFoldernames the save folder once. The Saves page, the .zip export andSaves.SharedSavePathnow use it rather than each joiningsavethemselves.docs/saves.md: one line each.Tests
python -I tests/test_launcher_core.py: 1742 checks passed. A new check inDeleteSaveChecks:SaveFolderisLongshotUser'ssaveon Windows and Linux, the folderImportTarget's profile is in.python -I tests/test_release.py: 37 tests OK.dotnet build App -c Release: 0 warnings, 0 errors.tools/screenshots.Screenshots
Before (#184's head) and after, in the comment below.
š¤ Generated with Claude Code
Screenshots: before and after
Drawn with
tools/screenshots(headless, the same scene and window size on both sides). Before is #184's head, so only this PR's change shows.The Saves page (
saves)Before: no way to the folder.
After: Open saves folder in the header, beside the slot count.
Settings, the builds folder row (
launcher-settings)Before: the path and Change.
After: a folder button at the end of the row. It's off in this scene, because the scene's builds folder hasn't been made: the tooltip says the first build makes it.
06bc35aec4b489bc5ca0Rebased onto main (
8594b47: #180, #171 and #179 merged). Only the language files and the screenshot tool's scene list conflicted, both sides adding entries; both kept, each catalog checked as JSON with no duplicate key, the app and the screenshot tool build with 0 warnings. The code is otherwise unchanged, so the earlier test runs stand. Merge order: #181, #182, #184, #185.b489bc5ca0acbcd2c366Description: the stack's merge order and the row's new name.
Rebased onto the reworked #184 (
d9f5559): this PR is its own commit again,acbcd2c. The Open builds folder button stays at the end of the builds folder row, which #184 renamed to BUILDS FOLDER with a hint saying what lives there. Conflicts were the Settings row's label and grid, the README's Settings sentence and the language files (both sides kept, #184's replaced texts removed, each file checked as JSON). Checks:test_launcher_core.py1799 passed,test_release.pyOK,dotnet build App -c Release0 warnings, 0 errors. Merge order: #182, #184, then this.The row after the rebase:
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.