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

forced correction #14

Open
Hjaf opened this issue May 13, 2020 · 2 comments
Open

forced correction #14

Hjaf opened this issue May 13, 2020 · 2 comments

Comments

@Hjaf
Copy link

Hjaf commented May 13, 2020

Backspace deletes the previous and correct key with enforced correction, shouldn't this emulate real life cursor position and behavior? While typing the correct key after a typo allows to continue, the real output will not actually correct the errors as the typo characters remain.

@hiamandeep
Copy link
Owner

You can disable 'forced correction' using the right sidebar menu. then it will give you your desired behavior.

@Hjaf
Copy link
Author

Hjaf commented May 13, 2020

I know, I thought the behavior in that mode would force the user to do the correction, not just type the correct key.

Is there a way to see the accuracy when correcting everything in non-forced mode? The error map shows some useful info, but i can't see a value that represents the errors made after the corrections, as the accuracy in this mode is 100% when everything is corrected.
I guess something like: ((total charcters in text)/(total keypressescharacters - total backspace keypresses))*100)

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

No branches or pull requests

2 participants