Consider presage upgrade path for v4
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 509
- PR merge metrics
- No merged PRs in 30d
Description
Optikey v4 will be a 64 bit application, so users who have set up presage will need to upgrade to a 64 bit version
We will need to
- ensure documentation updated to reflect this, and to point at the correct 64-bit version to install
- test the presage upgrade path, can users keep their existing database/model?
- test the optikey upgrade path - if someone is set up to use 32 bit presage, make sure Optikey doesn't crash, gives a helpful error and falls back to another prediction method (or none)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests, so start by tracing the v4 64-bit migration and existing presage setup. Check whether an existing presage database/model survives the upgrade, then verify OptiKey's behavior with 32-bit presage. Done means the documentation points to the correct 64-bit version, failures do not crash, the error is helpful, and fallback behavior is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100