yusufipk fa45c19d3b Match history and win rate ...

Every finished match goes into a small sqlite database: mode, deck, both
classes, result, turn count and who started. The result tag arrives in the
last turn of the match, so the record is written then, not when the game
object is closed (that only happens once the next match starts). The unique
key is the session directory plus the match start time, so importing old
session logs into the same database can be repeated without duplicates.

The new window (from the menu) shows the totals, the win rate by deck and by
opponent class, and the recent matches. Classes are drawn as hero portraits
cut from the card render, with the class colour as a placeholder until the
image is downloaded. Every table sorts by any column: the sort key is hidden
data, not the visible text, so dates, turn counts and results sort correctly,
and numeric columns start descending.

tools/import_history.py backfills the database from the session logs already
on disk, tests/test_history.py covers the date handling, the idempotency and
the win rate maths.

2026-07-28 00:04:24 +07:00

..

__init__.py

Hearthstone deck tracker for Linux, first public version

2026-07-27 22:31:13 +07:00

test_history.py

Match history and win rate

2026-07-28 00:04:24 +07:00

test_replay.py

Hearthstone deck tracker for Linux, first public version

2026-07-27 22:31:13 +07:00