fix(windows): the launcher starts on a PC that gives no default font, with its own Inter as the default (#123) #131
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!131
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/LongshotLauncher:fix/default-font"
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?
Some Windows 11 PCs give Avalonia no default font name (and no installed font to fall back on), so the launcher and its setup crashed before the first window with
Default font family name can't be null or empty, closing without a word after SmartScreen's Run anyway. Fixes #123.The launcher now names its bundled Inter, the font its windows already use, as Avalonia's default (
FontManagerOptions.DefaultFamilyName), so the system's default font isn't asked for. The screenshots tool uses the same options.Checked with a headless run whose font manager returns an empty default name and no installed fonts: without the change, the reporter's exact
InvalidOperationException; with it, the default resolves to Inter.tests/test_launcher_core.pyandtests/test_release.pypass. Nothing changes on screen (the windows already set Inter).🤖 Generated with Claude Code