aboutsummaryrefslogtreecommitdiff
path: root/src/app/js
diff options
context:
space:
mode:
author0neGal <mail@0negal.com>2024-04-29 18:59:28 +0200
committer0neGal <mail@0negal.com>2024-04-29 18:59:28 +0200
commit97be082dbbe66684f3e8a558e309329cad024e27 (patch)
treeaefaf1efb20d2ac121120eff588b28e994674d45 /src/app/js
parent9b31e6dfc2277dc2b904b4319b9bc06f849c38dc (diff)
downloadViper-97be082dbbe66684f3e8a558e309329cad024e27.tar.gz
Viper-97be082dbbe66684f3e8a558e309329cad024e27.zip
actual Linux launch support
The "Steam (Auto)" launch method should ideally work in all scenarios, ideally! Obviously, I can't and haven't tested in every environment, but I've attempted to make sure it functions. Launching Vanilla and Northstar works just fine, custom launch arguments also work just fine, it works with normal Steam, Flatpak Steam, and as a fallback with the Steam Browser Protocol (`steam://`) There's also the option to set your own/custom launch command for both the Vanilla and Northstar launch options. How well they work will of course depend on what the user set them to. "Steam (Auto)" attempts to pick the right Steam launch method depending on what's available, if the Steam executable can be found, it'll use "Steam (Executable)", if it cant and Flatpak is found on top of an install of Steam through Flatpak, then "Steam (Flatpak)" is used, if all of that fails, then we attempt to use "Steam (Protocol)" Some toasts will be shown if you attempt to run the game with either "Steam (Executable)" or "Steam (Flatpak)" and they cant find the game/Steam. This isn't an issue with "Steam (Auto)"
Diffstat (limited to 'src/app/js')
-rw-r--r--src/app/js/toast.js4
1 files changed, 4 insertions, 0 deletions
diff --git a/src/app/js/toast.js b/src/app/js/toast.js
index e0aba6b..501bf42 100644
--- a/src/app/js/toast.js
+++ b/src/app/js/toast.js
@@ -69,3 +69,7 @@ function dismissToast(id) {
}, 500)
}
}
+
+ipcRenderer.on("toast", (_, properties) => {
+ Toast(properties);
+})