Repository navigation
GWDGUI 3.4 — October 28, 2026
This release includes the changes since 3.3 and adds a Windows download.
- A formatted offline manual with contents navigation, styled text and search across wrapped words and table cells. Resizing preserves the active search match.
- A safer Windows build script: compile into a candidate directory, publish after success and recover an interrupted replacement. Fix Windows build-mode setup and compiler compatibility.
- Visible engine-start errors, guidance for paths copied from another operating system, and improved text rendering on Windows.
- Fix clicking past the end of notation lines and unnecessary PV refreshes.
- Introduce a game-neutral position/rules boundary, with independent regression fixtures, starting move-number metadata and game-specific timeout outcomes. GWDGUI remains an international-draughts application.
- Recreate README and the release-based changelog from the commit history. Remove the historical REFACTORING.md and REVIEW_NOTES.md from the current source tree and release bundles.
Downloads
- GWDGUI-3.4-linux-x86_64.tar.gz — extract into a writable directory and run
./gwdgui. GTK2 and SQLite3 runtime libraries are required. - GWDGUI-3.4-windows-x86_64.zip — extract into a writable directory and run
gwdgui.exe.
Both bundles include the executable, draughts font, current README, changelog, Markdown manual, license and BUILD-INFO.txt. Executables, font and manual are also available separately. SHA256SUMS covers all six download files. GitHub supplies source archives below.
The Linux executable was built from the clean v3.4 tag at 61c6cef, with the current manual embedded.
The Windows executable was supplied by the maintainer and is included unchanged. Its About text reports Build: source build; Commit: unavailable (source archive). Its embedded manual is the snapshot from that build; the separate and bundled MANUAL.md contain the final documentation cleanup.
Validation
Linux application build, headless regressions, GTK interface and tournament checks, lifecycle/DXP tests, default performance checks, source/archive audits and build-info checks passed. All 12 Windows batch recovery scenarios passed under Wine. Native Windows application execution was not part of these checks; Windows cross-compilation skipped because target compiler units were unavailable.
See the changelog and user manual.