As of v1, cursewords leaves all state considerations to the .puz files it opens. That covers a lot, but is likely too limiting for future feature development. A future version, maybe on the v2 branch, should save a settings file, which could:
I want to think about the best way to store these settings (and more) in a way that is portable, robust, and can be operated both with or without direct user input.
As of
v1,cursewordsleaves all state considerations to the .puz files it opens. That covers a lot, but is likely too limiting for future feature development. A future version, maybe on thev2branch, should save a settings file, which could:I want to think about the best way to store these settings (and more) in a way that is portable, robust, and can be operated both with or without direct user input.