Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More flexible solution character handling. #195

Merged
merged 1 commit into from
Aug 13, 2022

Conversation

jpd236
Copy link
Contributor

@jpd236 jpd236 commented Jul 29, 2022

  • Permit "*" as a valid grid character. While Across Lite doesn't
    support it, other formats do. It can't be entered directly (since it is
    bound as the shortcut for circling/uncircling a letter to match Across
    Lite), but it can be entered as a rebus.

  • When setting square text or solutions, never set the empty string,
    even if ToGrid returns one (due to an invalid character, namely a black
    square (".") or the symbol indicator ("[")). This ensures that bounds
    checks pass in HasSolutionRebus.

See #185

- Permit "*" as a valid grid character. While Across Lite doesn't
support it, other formats do. It can't be entered directly (since it is
bound as the shortcut for circling/uncircling a letter to match Across
Lite), but it can be entered as a rebus.

- When setting square text or solutions, never set the empty string,
even if ToGrid returns one (due to an invalid character, namely a black
square (".") or the symbol indicator ("[")). This ensures that bounds
checks pass in HasSolutionRebus.

See mrichards42#185
@mrichards42
Copy link
Owner

I'm a little less sure of this one since text stuff can be pretty fiddly, but logically it makes sense that we'd want to use the Blank value of " " since it's specifically called that, instead of "".

@mrichards42 mrichards42 merged commit 4ddd9cf into mrichards42:master Aug 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants