jessey
73f347449e
The recording banner gave no guidance, so it wasn't clear what to do after clicking Run Diagnostic. - Start dialog now spells out the flow: play the game, reproduce the crash, then Finish & analyze (data survives a hard freeze + reboot), with "Launch game & start" (steam.launch_game via steam:// appid URL) or "Start without launching". - Recording banner now states the next step, not just a sample count. - steam.launch_game(appid): best-effort Steam launch (steam / xdg-open). - Fix: escape "&" in button labels (Qt mnemonic) so "Finish & analyze" shows correctly instead of "Finish _analyze". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
27 lines
677 B
TOML
27 lines
677 B
TOML
[build-system]
|
|
requires = ["setuptools>=61"]
|
|
build-backend = "setuptools.build_meta"
|
|
|
|
[project]
|
|
name = "rigdoctor"
|
|
version = "0.13.0"
|
|
description = "Modular hardware monitoring & crash diagnostics for Linux gamers."
|
|
readme = "README.md"
|
|
requires-python = ">=3.11"
|
|
# Core/CLI/daemon are stdlib-only by design (D2). The GUI/tray modules will add
|
|
# PySide6 via an optional extra when those land.
|
|
dependencies = []
|
|
|
|
[project.optional-dependencies]
|
|
gui = ["PySide6", "pyte"]
|
|
|
|
[project.scripts]
|
|
rigdoctor = "rigdoctor.cli:main"
|
|
rigdoctor-gui = "rigdoctor.gui.app:main"
|
|
|
|
[tool.setuptools.packages.find]
|
|
where = ["src"]
|
|
|
|
[tool.setuptools.package-data]
|
|
rigdoctor = ["gui/assets/*.svg"]
|