satisfactorymodding / satisfactorymodding/SatisfactoryModManager
When launched via `smmanager://install` protocol invocation, the install mod action is ignored
Open
Nobody has claimed this yet.
- Dominant language
- Svelte
- Stars
- 500
- Forks
- 94
- Avg merge
- 9d 19h
- Merged PRs (30d)
- 2
Description
When the application is currently closed and the system opens it in order to handle the install call, the install action is lost, and must be triggered again
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the smmanager://install protocol handler and trace how the application processes the invocation during startup when no window is already open. Check the startup and install-action flow, then verify that launching the closed application through this protocol completes the install action without requiring a second invocation.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100