You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 27, 2023. It is now read-only.
The Hit-a-Hint character list used to determine/assign the labels is a hardcoded list in the code. Most other Hit-a-Hint mechanisms allow the user to set this list for themselves in the extension/add-on configuration.
For example, I personally dislike the semi-colon character since I find it hard to see when it's the second character in a 2-character hint. Having a configuration box in the extension/add-on settings for a sequence of characters that has a minimum required length and restrictions on what characters are allowed to be included would allow users to specify both their preferential order for the characters in the hinting, and add or limit what characters are used.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The Hit-a-Hint character list used to determine/assign the labels is a hardcoded list in the code. Most other Hit-a-Hint mechanisms allow the user to set this list for themselves in the extension/add-on configuration.
For example, I personally dislike the semi-colon character since I find it hard to see when it's the second character in a 2-character hint. Having a configuration box in the extension/add-on settings for a sequence of characters that has a minimum required length and restrictions on what characters are allowed to be included would allow users to specify both their preferential order for the characters in the hinting, and add or limit what characters are used.
The text was updated successfully, but these errors were encountered: